Brian, Thanks for the reply!
On Oct 28, 4:57 pm, Brian Gershon <[EMAIL PROTECTED]> wrote: > I just ran into this same issue. I eventually figured out that adding > TEST_DATABASE_NAME to settings.py (to prevent Django from using the > default memory database for sqlite) works around the issue. So do you just specify a filename and run your tests in sqlite, but non in an in-memory db? > > As far as debugging the memory database problem, I was getting the > "IntegrityError: django_content_type.name may not be NULL" error. > > I traced this down to this line: > > emit_post_sync_signal(models.get_models(), verbosity, interactive) > > in /django/core/management/commands/flush.py > > If I comment out that line, the error does not arise. Yeah, a coworker and I were finding the same thing... it's mysterious. Some of the tests run just fine, but on a few that line raises the error. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
