MySQL Forums
Forum List  »  InnoDB

Re: Question: Create table fails after switch from 4.0.18-4.1.10
Posted by: Noah White
Date: February 22, 2005 03:15PM

I found some posts regarding foriegn key contraint issues and came across the 'show INNODB status' command. Running that produced the following results:

------------------------
LATEST FOREIGN KEY ERROR
------------------------
050222 16:07:32 Error in foreign key constraint creation for table `virage_vs/vir_label_set_fields`.
A foreign key constraint of name `virage_vs/vir_field_type_fk`
already exists. (Note that internally InnoDB adds 'databasename/'
in front of the user-defined constraint name).
Note that InnoDB's FOREIGN KEY system tables store
constraint names as case-insensitive, with the
MySQL standard latin1_swedish_ci collation. If you
create tables or databases whose names differ only in
the character case, then collisions in constraint
names can occur. Workaround: name your constraints
explicitly with unique names.

From this I am gathering that my problem is due to the fact that FORIEGN KEY CONSTRAINT names must be unique in the scope of the database vs. the table now.

Thoughts?

-Noah

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Question: Create table fails after switch from 4.0.18-4.1.10
2037
February 22, 2005 03:15PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.