I want to use the test framework with my application, using postgresql/psycopg2.
I had the problem that any db error in any of my tests (including setups) would cause all following tests to fail (because the transaction was not rolled back). This was made even worse by the fact that I used the db in tearDown, which did not work very well either (I have since started using django.test.TestCase, so I don't use tearDown much). I also ran into this problem outside of tests, but do not remember details. Probably I was trying to use try ... except to catch a database error. My original solution was to edit base.py to enable autocommit (thus, as far as I can tell, disabling Django's transaction handling). This worked well for a while ... until I started using fixtures. Forward references don't work unless loaded within a transaction. I think the problem at the base of all this is that postgresql's transaction/error handling semantics are different from that of the other backends - while Django treats it as if it was the same. I would like to take a stab at fixing this (at the appropriate level, which I am not too sure I have identified). But before I do that, I would like to hear if anyone has any reasons why this should not be done ... I will post some test cases with suggested behavior later (in a ticket). If someone could give me a clue to how I can easily run the django test suite, I would be glad. Nis --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
