On Fri, May 1, 2009 at 9:02 PM, Charlie DeTar <cha...@gmail.com> wrote:
> I am indeed using the latest trunk (R10651). I'm actually not > particularly interested in testing commit or rollback; though thanks > for the pointer, that helps for the future. I'm really just > interested in testing cases which raise IntegrityError's. It seems > that any time an IntegrityError is produced, the postgres connection > becomes stuck. Subsequently, all attempts to access the database > result in the error: > Thing is, a side-effect of dealing with a test that raises an IntegrityError, using PostgreSQL, is you need a working rollback in order to recover. So, even though you may not be interested in actually testing rollback itself, you need it to work for this test to run properly. You need the call to actually get processed by the database, so that it will allow subsequent commands. And to get a working rollback, you need to use TransactionTestCase, not TestCase. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
