On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > 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.
Yes, you are right. Cite: Deviation from SQL standards: Like MySQL in general, in an SQL statement that inserts, deletes, or updates many rows, InnoDB checks UNIQUE and FOREIGN KEY constraints row-by-row. According to the SQL standard, the default behavior should be deferred checking. That is, constraints are only checked after the entire SQL statement has been processed. Until InnoDB implements deferred constraint checking, some things will be impossible, such as deleting a record that refers to itself via a foreign key. Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
