Re: Still getting IntegrityError in test fixture using dumpdata --natural

On Oct 12, 9:12 am, Russell Keith-Magee wrote: > --natural isn't a magic wand Dang! I knew that "magic removal" was a bad idea... > Contenttypes are automatically created by syncdb. If your fixtures > *also* contain content types, you can potentially get

Re: Still getting IntegrityError in test fixture using dumpdata --natural

On Wed, Oct 12, 2011 at 3:05 AM, bobhaugen wrote: > Replying to myself:  temporary fix for dumpdata: --exclude > contenttypes --exclude auth.permission This isn't a temporary fix -- it's the *actual* fix. > The result now works as a test fixture. > > Not sure what to

Re: Still getting IntegrityError in test fixture using dumpdata --natural

Replying to myself: temporary fix for dumpdata: --exclude contenttypes --exclude auth.permission The result now works as a test fixture. Not sure what to conclude: * the fix for issue #7052 does not work? * --natural does not fix the IntegrityErrors with contenttypes in test fixtures? *

Still getting IntegrityError in test fixture using dumpdata --natural

Still getting "IntegrityError: columns app_label, model are not unique" when loading a test fixture created by dumpdata using the keyword --natural. I am probably missing something, but I understood the resolution to https://code.djangoproject.com/ticket/7052 to be to use the new -- natural