Hi,
> How do I execute the following UPDATE statements such that I can ensure
> that all integrity constraints are maintained upon the completion of the
> last one?
> UPDATE test_parent SET id = 6 WHERE id = 1;
> UPDATE test_child SET parent_id = 6 WHERE parent_id = 1;
And would specif
tables
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: "Matthew Bogosian" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Saturday, January 24, 2004 4:11 AM
Subject: Re: Postponing Integrity Checking...
> On Fri
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't is still in a failed
>>stat
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't is still in a failed state. In other
Right. You're not supposed to use it
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't is still in a failed state. In other
words, I could screw up and so something like:
SET FOREIGN_KEY_CHECKS = 0;
At 15:52 -0800 1/23/04, Matthew Bogosian wrote:
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
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,
