Hi Chris, 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.
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. -Brian On Oct 25, 9:50 am, "Chris H." <[EMAIL PROTECTED]> wrote: > I've noticed at work and with my personal code that since the upgrade > to Django 1.0 that I'm getting test failures when I run the unit tests > under a SQLite :memory: database. > > I thought it might be something to do with those two codebases, so > this morning I started a fresh project and I'm seeing the same > problem. > > Is anyone else seeing this... the steps I took to reproduce were: > 1. django-admin startproject sqlitetest > 2. Edit sqlitetest/settings.py: > DATABASE_ENGINE = 'mysql' > DATABASE_NAME = 'sqlitetest_local' > DATABASE_USER = '(your awesome username)' > DATABASE_PASSWORD = '(your awesome password)' > DATABASE_HOST = '' > DATABASE_PORT = '' > > INSTALLED_APPS = ( > 'django.contrib.admin', > 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > ) > 3. django-admin.py syncdb > 4. django-admin.py test > (tests pass) > 5. Create a settings_test.py file: > from settings import * > DATABASE_ENGINE = 'sqlite3' > DATABASE_NAME = ':memory:' > DATABASE_USER = '' > DATABASE_PASSWORD = '' > DATABASE_HOST = '' > DATABASE_PORT = '' > 6. Run tests, get 3 errors (the rest pass): > IntegrityError: django_site.domain may not be NULL > IntegrityError: auth_permission.name may not be NULL > IntegrityError: django_content_type.name may not be NULL > > It's kind of a bummer because the tests run so much faster against > a :memory: database and I didn't know if anyone had encountered this > yet? > > Thanks, > > Chris H. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
