-
Notifications
You must be signed in to change notification settings - Fork 933
Test case and fix to NH-3898 #500
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
Conversation
If this patch get merged, it would be probably more likely to happen on master or 4.1 branch. If you port your PR on master, now it requires VS2017 (Community edition is enough). The change looks legit, but you need to follow contributing guidelines. Notably, use tabs instead of spacing. |
ed8051b
to
e89e9db
Compare
(https://nhibernate.jira.com/browse/NH-3898) Configuring a property with generated="insert" it makes "Property.IsUpdatable" "false" even using update="true" in the xml mapping file. Please consider keep this issue as Critical, as it does not break the application, it makes the applications migrated from NHibernate version 2 to 3 or 4 generates inconsistent data within the database. As soon as I can, I will send a pull request
…the property is not yet set to the actual inserted value db side.
e89e9db
to
056912b
Compare
Re-based for fixing the release build, small additional fix added to test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to regenerate async
Assert.That(employee.PromotionCount, Is.EqualTo(0)); | ||
employee.Name = "Employee 1 changed"; | ||
employee.PromotionCount++; | ||
Assert.That(employee.PromotionCount, Is.EqualTo(1)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That assert does not make sense anymore.
Thanks |
Test case and fix to NH-3898
Configuring a property with generated="insert" it makes
"Property.IsUpdatable" "false" even using update="true" in the xml
mapping file.
Please consider keep this issue as Critical, as it does not break the
application, it makes the applications migrated from NHibernate version
2 to 3 or 4 generates inconsistent data within the database.