Many thanks for a very helpful response!! At this point, I assume the proper practice is to create the users in a setup() method when unittesting instead of assuming they'll be brought up automatically when testing. (Sorry, it's been a long day - I hope that makes sense.)
On Mon, Jun 16, 2008 at 4:24 PM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > On Mon, Jun 16, 2008 at 11:36 AM, ristretto <[EMAIL PROTECTED]> wrote: >> >> I'm running into this too. Can someone confirm this related to MySQL >> InnoDB tables or not? > > This is unrelated to MySQL or InnoDB (although that configuration will > cause some difficulties with fixtures that have circular dependencies > in their related objects). > > The errors you are seeing are due to ticket #7052. See the ticket for > more details. > > This won't be an easy thing to fix, so in the interim, the workaround > is to omit auth and contenttypes from the serialized fixtures. We > recently added an --exclude option to dumpdata to allow you to do this > easily. > > Yours, > Russ Magee %-) > > > > -- Picante Solutions Limited e: [EMAIL PROTECTED] w: 06 757 9488 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
