Yes, that's right. Deferrable is all about transactions. A lone-statement that is not explicitly enclosed in a BEGIN-COMMIT block is itself an implicit transaction. Deferred foreign key constraints get enforced at the COMMIT and the COMMIT is implicitly executed with a lone-statement, so the constraints should be enforced. This is what happens unless you reproduce the specific circumstances that I described.
Steve -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Jan Sent: Saturday, January 22, 2011 9:48 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Deferred foreign key constraint bug? Am 21.01.2011 21:36, schrieb Steve Campbell: > To summarize, to reproduce this problem, the statements must not be enclosed > in a BEGIN-COMMIT block. But DEFERRABLE is all about transactions, isn't it? As far as I understand this feature... I use it a lot, because then I have no headache importing data (order does not matter any more). Jan _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
