On Mon, Jul 8, 2013 at 4:14 PM, Larry Martell <larry.mart...@gmail.com> wrote: > It appesars it's trying to add a row to django_content_type and it's > already there. I tried not loading the fixture for django_content_type > but I got the same error. These fixture files contain data I dumped > from my real db, so I know it's good. Googling this I found a few > posts with people having the same problem, but they are all a few > years old. People 'solved' this by using an external package > (django-fixture-magic) or excluding the auth tables or hand > re-ordering the records in the fixtures file. None of these seem like > good solutions to me. Is this still a known problem? Shouldn't I be > able to load data generated from a dump?
rigth, it's quite messy. i usually don't use dump files. (the mess, they don't do so 'clean' tests). check 'natural keys' (https://docs.djangoproject.com/en/1.5/topics/serialization/#natural-keys) for a ways to get more robust fixtures -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
