wasn't a DB cache issue in my case, just a bug in my model code. The first run of unittest silently failed, and subsequent ones showed the above stack trace.
Running stuff in the python interpreter helped find the problem. I do a connection._rollback() at the start of my unittest now, as insurance. /Nara --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
