Jira issue originally created by user mkoonstra:
Two entities: A and B
Situation: A.b is null and set to eager loading (with fetch="EAGER"), find(id) is called for object A
Actual Behaviour: The record from A is not found (probably due to an INNER JOIN being used).
Expected behaviour: Entity A is loaded with b set to null (like during lazy loading).
Comment created by @guilhermeblanco:
It seems to be associated with this commit:
Since it's a crash between versions, I'm increasing priority and also marking as regression.
Comment created by @beberlei:
A blocker indeed, reschedulding RC1 release until this is fixed.
Can you show us the mappings, specifically how you map A#b? Are you setting nullable=false on the join columns?
You problem could be related to:
I was unable to reproduce your issue with the comments you made so far.
Are you able to modify the attached test file into a failure state that represents your problem?
It may be easier for us to track down your problem after that.
Comment created by mkoonstra:
Trying the test case on master, but can't seem to be able to reproduce the bug (same goes for the actual problem case)
Maybe some code has changed allready? I will investigate further if I can reproduce the bug in master.
Closing as invalid, please reopen if you can reproduce, but it seems this is fixed.
Issue was closed with resolution "Invalid"
Imported 1 attachments from Jira into https://gist.github.com/663fcfa957f0b78e0750