-
Notifications
You must be signed in to change notification settings - Fork 936
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
Fetching a lazy loaded component regression #3164
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Thanks, I'm glad you can reproduce.
Yeah I know but I found it easier to modify if it was all within 1 file. |
Test case https://github.com/bahusoid/nhibernate-core/tree/gh3164. Not sure but seems regression from #1922 |
Fixed by #3171 |
Great, thanks @bahusoid. |
I have identified a regression introduced in version 5.3.0. It happens when trying to fetch a lazy loaded component which has a read-only property and is mapped as an interface.
It's a little querky to explain but I've tried to produce a minimal sample to show you the issue.
Please see the attached application (making sure to set the connection string). The database must have the following structure:
SQL above edited after realising that the table must have data to reproduce.
Exception:
Test NHibernate.zip
The text was updated successfully, but these errors were encountered: