Skip to content
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

ISession.IsDirty() shouldn't throw exception for transient many-to-one object in a session #1419

Closed
bahusoid opened this issue Nov 2, 2017 · 0 comments

Comments

@bahusoid
Copy link
Member

bahusoid commented Nov 2, 2017

As suggested in #1413 (comment)
I extracted separate issues.

Current behavior: TransientObjectException is thrown by ISession.IsDirty() call when transient many-to-one object is present in session
Expected behavior: ISession.IsDirty() should not throw exception

Technical details of the problem is here.

@hazzik hazzik changed the title ISession.IsDirty() shouldn't throw exception for transient many-to-one object in session ISession.IsDirty() shouldn't throw exception for transient many-to-one object in a session Nov 2, 2017
@hazzik hazzik modified the milestone: 5.1 Nov 2, 2017
bahusoid added a commit to bahusoid/nhibernate-core that referenced this issue Nov 3, 2017
hazzik pushed a commit that referenced this issue Nov 3, 2017
…1420)

Add an explicit check for transient objects in ManyToOne.IsDirty

Fixes #1419
@fredericDelaporte fredericDelaporte added this to the 5.0.1 milestone Nov 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants