Well, there are some ways around it if you use dumpdata/loaddata statements. But for initial fixtures, it causes trouble. When the DB is created, django will dynamically try to populate the content-types table. But if you are already putting data into that table, the primary keys will clash.
When doing your dumpdata, you can try excluding the contenttypes app and see if that resolves your issues. (it might cause other issues if you have models that depend specifically on the primary keys of the contenttypes). ./manage.py dumpdata --exclude contenttypes > initial_fixture.json On Jun 14, 10:06 am, Amit Sethi <amit.pureene...@gmail.com> wrote: > On Tue, Jun 14, 2011 at 8:00 PM, christian.posta<christian.po...@gmail.com> > wrote: > > Yes, it is. Any reason why you want the content-types to be part of > > your fixtures? Why not let django build that up by itself? > > Well essentially it was just a dumpdata from earlier that is being > used. But why should I not have it as part of fixtures ? > > -- > A-M-I-T S|S -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
