On Fri, 2008-03-07 at 09:58 -0800, meppum wrote: > I've been playing with Django for a while now, learning the ropes and > such. I started building some unit tests using the django TestCase > classes, but recently I've hit a snag with using Postgres as the > backend to my tests and testing database exceptions.
Before anybody points this back to django-users, I asked Meppum to post here. It requires some design work. Because the test framework uses a single database connection throughout, it's not too hard to trip it up, so we need to think about where the boundaries are and what people need to do in their tests (plus, whether we're missing some support internally). I spent more than a few hours chasing a similar problem with queryset-refactor last weekend where we now manually reset the connection at the end of a test. Maybe that's the best that can be done, in which case we just document it. No biggie. Maybe we can behave better in the default case, though. Malcolm -- Always try to be modest and be proud of it! http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
