-
Notifications
You must be signed in to change notification settings - Fork 933
Property-ref on many-to-one with composite id fails #1918
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Property-ref on many-to-one with composite id fails #1918
Conversation
src/NHibernate.Test/NHSpecificTest/EmbIdBidirectional/BiEmbIdRefEdEntity.cs
Outdated
Show resolved
Hide resolved
src/NHibernate.Test/NHSpecificTest/EmbIdBidirectional/Fixture.cs
Outdated
Show resolved
Hide resolved
src/NHibernate.Test/NHSpecificTest/EmbIdBidirectional/Fixture.cs
Outdated
Show resolved
Hide resolved
src/NHibernate.Test/NHSpecificTest/EmbIdBidirectional/Fixture.cs
Outdated
Show resolved
Hide resolved
It is likely to be caused by #1872. |
#1872 has introduced a call to //note that this implementation is kinda broken
//for components with many-to-one associations
return ResolveIdentifier(value, session, owner); It does not tell what is the trouble, but maybe that is what causes the failure here and has to be fixed. I am checking this. |
I have pushed the reviewed changes, and I have added a fix. |
I have updated the title and description for more closely matching the actual issue. This issue is not specific to one-to-one. |
NHibernate fails loading an entity when it has a many-to-one which use a composite-id foreign key and is referenced by a property-ref.
Regression bug. Didn't exist in 5.1.x.
Found it when I upgrading Envers project to use NH Core 5.2 => similar test fails there as well now.