-
Notifications
You must be signed in to change notification settings - Fork 619
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
Model changed? still returns true after being synchronized #123
Comments
activerecord-import 0.5.0 has been pushed to rubygems with this in there. Thanks again! |
In rails 4.1 and 4.2 I have been getting errors like: #Class:0x00000002e2ead0#test_#import with :synchronize option synchronizing on destroyed records with explicit conditions_reloads data for existing in-memory instances: #Class:0x00000002e2ead0#test_#import with :synchronize option synchronizing on destroyed records with explicit conditions_reloads data for existing in-memory instances: #Class:0x00000002e81438#test_.synchronize_reloads data for the specified records: #Class:0x00000002e81438#test_.synchronize_reloads data for the specified records: #Class:0x00000002e81438#test_.synchronize_the synchronized records aren't dirty: #Class:0x00000002e81438#test_.synchronize_the synchronized records aren't dirty: #Class:0x00000002e2bc40#test_#import with :synchronize option synchronizing on new records with explicit conditions_reloads data for existing in-memory instances: Changes to #synchronize fixes this for rails 4.1, but breaks it for rails 3.2. |
…fter synchronizing models
After importing models using the synchronize option calling
model.changed?
still returns true e.g.Looks like a pretty straightforward fix by adding
instance.changed_attributes.clear
in synchronize.rb. I'd be happy to put together a pull request if you agree this is a bug.The text was updated successfully, but these errors were encountered: