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

act_as_paranoid integrity breakage for deployment #387

Open

martinpovolny opened this issue Jan 28, 2013 · 1 comment

Assignees

Labels

bug

martinpovolny commented Jan 28, 2013

due to the use of acts_as_paranoid in Deployments the the FK constraints cannot not be there (the referenced entities do not use acts_as_paranoid)

example problem: (soft) deleting a deployment and then deleting a pool could lead to a link to an non-existent pool from a deployment etc.

funny point is no test fails :-(

ghost assigned martinpovolny

Author

martinpovolny commented Feb 6, 2013

the solution will be along the idea of

expanding the "soft-delete zone" in conductor ER model
NULLifying the relations that cross the soft-delete border in the model
adding FKs to really enforce the relation

martinpovolny mentioned this issue

act_as_paranoid integrity breakage for instances #386

Open

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