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.

Sign up for GitHub

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

Jump to bottom

Fix a record being dirty after destroying it #135

Merged

mvz merged 1 commit into master from not-dirty-after-destroy

Oct 22, 2019

Contributor

mvz commented Oct 22, 2019 •

edited

Part of #108, fixing the following issue:

A record is dirty after being destroyed. and Rails therefore considers that there are still changes to be saved to the database. Thus, if an after_destroy callback modifies the deleted record again, this may trigger new unwanted callbacks. Moreover, this prevents a record to be recovered after being destroyed without reloading it.


          Added some consistency on paranoid_value between destroy, delete and …

c5fbba9

…destroy_fully!

Fix a record being dirty after destroying it.

mvz merged commit 22f1244 into master

mvz deleted the not-dirty-after-destroy branch

October 22, 2019 11:05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment