Re: Difference between sqlite3 and mysql backend on test code involving generic relationships

Well, it seems to happen, when the post_syncdb signal code from django.contrib.auth is called. Somehow calling the code from ./manage.py test differes from ./manage.py flush. I think I will reproduce this in a minimal django project and try file a bug report. Best regards, Oliver -- Oliver

Re: Difference between sqlite3 and mysql backend on test code involving generic relationships

I looked a bit deeper into this issue, and so far I can say, that the exception is raised by django.test.TestCase in the method _pre_setup. call_command('flush', verbosity=0, interactive=False) is where it originates. Calling ./manage.py flush on the command line works like a charm. I also have to

Difference between sqlite3 and mysql backend on test code involving generic relationships

Hi, I encounter strange differences when I run my test code against sqlite3 and against mysql. I am about to test it with Postgresql later today. My models make heavy use of generic relationships. And everytime I run "./manage.py test" with the mysql backend I receive the following error.