bject: Re: FOREIGN KEYs and ALTER TABLE
>On Thu, Jan 03, 2002 at 05:21:49PM +0200, Heikki Tuuri wrote:
>: mysql> CREATE TABLE parent(id INT NOT NULL, PRIMARY KEY (id))
TYPE=INNODB;
>: Query OK, 0 rows affected (0.11 sec)
>:
>: mysql> CREATE TABLE child(id INT,
On Thu, Jan 03, 2002 at 05:21:49PM +0200, Heikki Tuuri wrote:
: mysql> CREATE TABLE parent(id INT NOT NULL, PRIMARY KEY (id)) TYPE=INNODB;
: Query OK, 0 rows affected (0.11 sec)
:
: mysql> CREATE TABLE child(id INT, parent_id INT, INDEX par_ind (parent_id),
: -> FOREIGN KEY
> Hrmm. Is that a "feature" that's planned to be fixed. Obviously,
> if you have a table with thousands or millions of rows in it, ALTER
> TABLE is a lot easier than copying the table to a temp table,
> dropping the original table, creating a new table, and copying the
> data back in.
Actu
Hi!
-Original Message-
From: Philip Molter <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, January 03, 2002 3:21 PM
Subject: Re: FOREIGN KEYs and ALTER TABLE
>On Thu, Jan 03, 2002 at 01:48:21PM +020
On Thu, Jan 03, 2002 at 01:48:21PM +0200, Heikki Tuuri wrote:
: Hi!
:
: This is a feature (= documented bug). Look at
: http://www.innodb.com/ibman.html:
: ...
: Updated December 13, 2001: Added a note that you should not do an ALTER
: TABLE to a table which has or is referenced in a foreign key
Hi!
>With InnoDB tables under 3.23.4x, if you perform an ALTER TABLE on
>a table, any foreign key declarations that point to that table fail
>to work (they always return a failure).
>
>Is this a known bug? I don't see it on the InnoDB todo or bug
>list, but I seem to remember hearing about it al
With InnoDB tables under 3.23.4x, if you perform an ALTER TABLE on
a table, any foreign key declarations that point to that table fail
to work (they always return a failure).
Is this a known bug? I don't see it on the InnoDB todo or bug
list, but I seem to remember hearing about it already.
* P
