ISession.IsDirty() should not throw exception on new ManyToOne object in session #1416
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@bahusoid you may wish to integrate this PR to the PR with tests. |
|
@hazzik Could you please clarify. Are you suggesting to close this PR and simply add this commit to PR with the tests? |
|
Yes, pretty much. |
|
Ok. It's done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix one of the cases in #1413.
Fixed case - exception is thrown by ISession.IsDirty() call when new ManyToOne object present in session. Fixed test case - SessionIsDirtyShouldNotFailForNewManyToOneObject in #1414:
https://github.com/nhibernate/nhibernate-core/pull/1414/files#diff-1c250a6682b3027be99e132c9257cb4dR72