On Fri, Jan 15, 2010 at 9:59 AM, Vitaly Babiy <vbabi...@gmail.com> wrote: > I have also been thinking about this, I think there is one problem but I am > not sure. This is when you have functional test and they need talk to a > database. In most cases you will be using transactions which should be fine, > but if for some reason you can't use transaction for test this will have to > run each one on its own.
The other way to skin this particular cat is to have multiple test databases, one for each thread. This approach would require a lot more modifications to the existing test framework (to set up and allocate individual tests/test cases to each database), but it would guarantee that threads didn't end up with contention or corruption over a single database. Yours, Russ Magee %-)
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
