-
Notifications
You must be signed in to change notification settings - Fork 195
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
Domain classes marked as dirty without changes on them #1307
Comments
It looks like this is happening because when you call |
@puneetbehl I don't really understand why it is intended since there is no changes to the actual domain entity. The javadoc of the hasChanged method states that it returns true if the instance has changes. But there are no actual changes. I think the problem is here (or in the code that initializes this field - maybe there are cases where it is not initialized so its null): |
I am sorry for the confusion. I believe you are right and the problem is the association proxy also has a field I will soon push a fix for this and testing each of the underline implementations. |
* Moved DirtyCheckingSpec to tck. * Added some more test to the suite to verify that dirty checking is working fine with initialized proxies.
* Moved DirtyCheckingSpec to tck. * Added some more test to the suite to verify that dirty checking is working fine with initialized proxies.
Domain classes are marked as dirty when any operations are done on the grails.web.databinding.WebDataBinding#getProperties, without actually changing any property.
Task List
Steps to Reproduce
Expected Behaviour
Domain classes should not become dirty without actual changes on them.
Actual Behaviour
Domain classes are marked as dirty without actual changes on them.
Environment Information
Example Application
The text was updated successfully, but these errors were encountered: