On Thu, Jun 19, 2008 at 3:44 AM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>> from what that says I'd guess you are using the InnoDB MySQL storage backend, > > Right you are. That limitation is a bit of a pain. Yes, it is. Unfortunately, the best way to fix this is for MySQL to either (1) implement transaction level key integrity checks, or (2) provide a way to manually disable and re-enable integrity checks. If someone with more MySQL-fu than me knows how to do either of these things, let me know and we can put this bug to bed. There is one thing _we_ could do - drop all the constraints before loading a fixture, then re-create the constraints after loading the fixture. However, this would require a lot of work to implement. I'm not particularly interested in doing this work myself (it's an itch I just don't have), but if someone else wants to take the lead, they would be warmly received. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
