On Thu, Nov 26, 2009 at 9:37 PM, Jani Tiainen <[email protected]> wrote: > On Thu, 2009-11-26 at 20:23 +0800, Russell Keith-Magee wrote: > >> * Do you still get the same failures if you convert QueryTestCase into >> a TransactionTestCase (i.e., change the import "from django.test >> import TestCase" to "from django.test import TransactionTestCase as >> TestCase") > > All three passed in isolated tests.
Do the TransactionTestCase versions still pass when you execute the full multi-db suite? If so, I think we have narrowed the problem down to the rollback code. A few more debug data points: * Could you please run the full multi-db suite with verbosity=2; it would be helpful to see the exact order in which the tests are being executed * Could you run just the multiple_database.QueryTestCase test case (again, with verbosity=2, so I can see the test order). I'm wondering if the problem might be a leakage of fixture loading. Thanks, Russ %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
