Re: Postponing Integrity Checking...

2004-01-23 Thread Matthew Bogosian
On Fri, 23 Jan 2004, Paul DuBois wrote: >At 17:32 -0800 1/23/04, Matthew Bogosian wrote: >>Although this does the trick (kind of), this just turns off integrity >>checking for that session, right? When I turn it back on, any >>statement that would have failed but didn&#

Re: Postponing Integrity Checking...

2004-01-23 Thread Matthew Bogosian
FOREIGN KEY (parent_id) REFERENCES test_parent (id) ON DELETE CASCADE POSTPONE FOREIGN_KEY_CHECKS UNTIL COMMIT ) TYPE = INNODB; Or something like that. Of course if auto-commit is on, then the behavior would be unchanged. --Matt On Fri, 23 Jan 2004, Paul DuBois wrote: >At

Postponing Integrity Checking...

2004-01-23 Thread Matthew Bogosian
I searched the archives and the manual for an answer to this, but I haven't found an answer. I have several InnoDB tables: CREATE TABLE test_parent ( id INTEGER NOT NULL PRIMARY KEY ) TYPE = INNODB; CREATE TABLE test_child ( id INTEGER NOT NULL PRIMARY KEY,