Sporadic proxy deletion failures on mysql
|Reported by:||nate_b||Owned by:||nate_b|
|Component:||Database layer (models, ORM)||Version:||1.4-beta-1|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
regressiontests.delete_regress.tests.ProxyDeleteTest and regressiontests.delete_regress.tests.ProxyOfProxyDeleteTest
sporadic IntegrityErrors would occur. This was caused by the proxy model's base model not having the proxy model as a dependancy, and the sporadic nature was entirely the result of dictionary ordering going into Collector.sort() - sometimes it would be in an order that honored the constraints, sometimes it wouldn't.
This was introduced, I believe, in revision 17664. I have only observed it on mysql, but it is hypothetically a universal issue.
My proposed solution is simply to ensure that the proxy model's base class gets included as a dependency.