On Thu, Jun 19, 2008 at 9:04 PM, Peter Melvyn <[EMAIL PROTECTED]> wrote: > > On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > >> (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 > > It should work: > > SET FOREIGN_KEY_CHECKS = 0;
Yes - the ticket for this problem (#3615) already has a patch that uses this technique. However, I was under the impression that this has the effect of disabling, not just deferring key checks - that is, if you disable checks, load bad data, then re-enable checks, no errors will be raised. We don't want to be responsible for breaking the referential integrity of a database, so this isn't a viable solution. If I've misunderstood the behaviour of SET FOREIGN_KEY_CHECKS, or you have any other suggestions, let me know - I'd very much like to put this bug behind us. 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 [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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
