Re: Foreign Key Error

2011-02-14 Thread Victor Subervi
gt; -Original Message- > From: Victor Subervi [mailto:victorsube...@gmail.com] > Sent: Monday, February 14, 2011 3:09 PM > To: mysql@lists.mysql.com > Subject: Foreign Key Error > > Hi; > I have this command: > > create table if not exists categoriesRelationships (ID

RE: Foreign Key Error

2011-02-14 Thread Gavin Towey
2011 3:09 PM To: mysql@lists.mysql.com Subject: Foreign Key Error Hi; I have this command: create table if not exists categoriesRelationships (ID integer auto_increment primary key, Store varchar(60), Parent integer not null, foreign key (Parent) references categories (ID), Child integer not nul

Foreign Key Error

2011-02-14 Thread Victor Subervi
; show innodb status prints out this: LATEST FOREIGN KEY ERROR 110214 15:03:43 Error in foreign key constraint of table test/categoriesRelationships: foreign key (Parent) references categories (ID), Child integer not null, foreign key (Child

Re: Help Foreign Key Error

2005-07-01 Thread SGreen
"Scott Purcell" <[EMAIL PROTECTED]> wrote on 07/01/2005 03:46:49 PM: > Hello, > > > MYSQL on PC v 4.0.15 > > And I am trying to add an address table off of it. Using the > users(id) as a primary key and deleting on cascade. So when the user > is deleted from system, so are the addresses associ

Help Foreign Key Error

2005-07-01 Thread Scott Purcell
Hello, MYSQL on PC v 4.0.15 And I am trying to add an address table off of it. Using the users(id) as a primary key and deleting on cascade. So when the user is deleted from system, so are the addresses associted with him. // code that errors CREATE TABLE `address` ( `id` int(11), `create

Re: Foreign Key Error 1005:150

2004-12-06 Thread Heikki Tuuri
Steve, - Original Message - From: <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Monday, December 06, 2004 1:00 PM Subject: Re: Foreign Key Error 1005:150 --NextPart_Webmail_9m3u9jl4l_14802_1102330771_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit M

RE: Foreign Key Error 1005:150

2004-12-06 Thread Kocsis, Bela
PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, December 05, 2004 2:42 PM To: [EMAIL PROTECTED] Subject: Foreign Key Error 1005:150 I am unable to define a foreign key with the following three tables. I am unable to find the error having searched the documentation and tried several variations

Re: Foreign Key Error 1005:150

2004-12-06 Thread steven . p . long
Michael, Thank you for your reply. Here is a bit more info. I changed the default table type to innodn in the my.ini file before creating the database, so all tables are innodb. I tried the create statements with and without explicit index clauses with all permutations - same result each tim

Re: Foreign Key Error 1005:150

2004-12-05 Thread Michael Stassen
Something is wrong, but it's hard to say what. It seems unlikely you entered exactly those commands and got an error only on the last ALTER TABLE. First, you need InnoDB tables to support foreign keys, but you don't specify the table engine in your CREATE statements. The default is MyISAM, unle

Re: Foreign Key Error 1005:150

2004-12-05 Thread Heikki Tuuri
ql> Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php - Original Message - From: <[EMAIL PROTECTED]> Newsgr

Foreign Key Error 1005:150

2004-12-05 Thread steven . p . long
I am unable to define a foreign key with the following three tables. I am unable to find the error having searched the documentation and tried several variations. Note that I created the first two tables with and without the index clause in the table ddl with no difference in outcome. The t

Re: Foreign key error

2004-10-13 Thread Michael Stassen
:perror 150 MySQL error: 150 = Foreign key constraint is incorrectly formed This is usually due to a missing index. To make a foreign key, both of the involved columns must come first in an index. Do you have indexes on msg_recipients.recipient_member_id and members.id? Michael [EMAIL PROTECT

Re: Foreign key error

2004-10-13 Thread SGreen
run the command: SHOW INNODB STATUS; whenever you get those errors and it will give you more details. Shawn Green Database Administrator Unimin Corporation - Spruce Pine Herman Scheepers <[EMAIL PROTECTED]> wrote on 10/13/2004 03:42:34 PM: > I tried to create a foreign key using: > > ALTER TABL

Foreign key error

2004-10-13 Thread Herman Scheepers
I tried to create a foreign key using: ALTER TABLE msg_recipients ADD CONSTRAINT msg_recipient_member_fk FOREIGN KEY (recipient_member_id) REFERENCES members (id); and got this error: Can't create table '.\wapmagic\#sql-c50_48.frm' (errno: 150) Any ideas? Thanx Herman _

Re: MySQL 4.0.15 : Foreign Key - ERROR 1005 (errno: 150)

2004-05-06 Thread Victoria Reznichenko
Andy Jefferson <[EMAIL PROTECTED]> wrote: > > I've got 2 tables in a circular dependency as follows > > CREATE TABLE USERDETAILS > ( >USERDETAILS_ID BIGINT NOT NULL, >FORENAME VARCHAR(30) BINARY NULL, >SURNAME VARCHAR(30) BINARY NULL, >USER_USER_ID_OID BIGINT NULL, >PRIMARY KE

MySQL 4.0.15 : Foreign Key - ERROR 1005 (errno: 150)

2004-05-05 Thread Andy Jefferson
Hi, I've got 2 tables in a circular dependency as follows CREATE TABLE USERDETAILS ( USERDETAILS_ID BIGINT NOT NULL, FORENAME VARCHAR(30) BINARY NULL, SURNAME VARCHAR(30) BINARY NULL, USER_USER_ID_OID BIGINT NULL, PRIMARY KEY (USERDETAILS_ID) ) TYPE=INNODB CREATE TABLE `USER`

Re: InnoDB - Foreign Key - Error 150.

2004-05-05 Thread Victoria Reznichenko
"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote: > Victoria=20 > > That seemed to work well, thank you. > > However, I received another error that I am not sure how to troubleshoot = > during the restore: >ERROR 1114 at line 83 in file: = > '/bb/bin/mysql/backups/archive_4320.sql': The table

Re: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Luciano Barcaro
and I used the "--disable-keys" command, believing this would correct the problem. Do you know why it does not? No, the foreign key error is generated because mysqldump dumps table in a different order (alphabetical) that it should. I know I asked a bunch of questions, thanks for wha

RE: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Tucker, Gabriel
: InnoDB - Foreign Key - Error 150. Victoria That seemed to work well, thank you. However, I received another error that I am not sure how to troubleshoot during the restore: ERROR 1114 at line 83 in file: '/bb/bin/mysql/backups/archive_4320.sql': The table 'cur_reject_

RE: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Tucker, Gabriel
n I do here? Thanks - Gabe -Original Message- From: Victoria Reznichenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 10:35 AM To: [EMAIL PROTECTED] Subject: Re: InnoDB - Foreign Key - Error 150. "Tucker, Gabriel" <[EMAIL PROTECTED]> wrote: > Marvin > > I

Re: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Josh Trutwin
On Tue, 4 May 2004 11:01:59 -0400 "Tucker, Gabriel" <[EMAIL PROTECTED]> wrote: > Luciano > > I am confused... As far as I can tell, the set > foreign_key_checks=0; is used with the load data infile command. Actually, I think that it is used for all operations on the DBMS, not just load data

RE: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Tucker, Gabriel
: [EMAIL PROTECTED] Subject: Re: InnoDB - Foreign Key - Error 150. "Tucker, Gabriel" <[EMAIL PROTECTED]> wrote: > Marvin > > I believe that is the problem with the restore. When I create the = > archive file using the mysqldump command and options previously listed, =

RE: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Tucker, Gabriel
L PROTECTED] Sent: Tuesday, May 04, 2004 10:03 AM To: Tucker, Gabriel Subject: Re: InnoDB - Foreign Key - Error 150. Put in your script: set foreign_key_checks=0; in the first line. mysqldump dumps tables in alphabetical order. Tucker, Gabriel wrote: > Hello All: > > I am having a p

Re: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Victoria Reznichenko
"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote: > Marvin > > I believe that is the problem with the restore. When I create the = > archive file using the mysqldump command and options previously listed, = > I get the create table in the order listed below and thus, the foreign = > key constraint is

Re: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Ken Menzel
e end! Best of luck, Ken - Original Message - From: "Marvin Wright" <[EMAIL PROTECTED]> To: "Tucker, Gabriel" <[EMAIL PROTECTED]>; "Mysql General (E-mail)" <[EMAIL PROTECTED]> Sent: Tuesday, May 04, 2004 10:22 AM Subject: RE: InnoDB - Foreign Key -

Re: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Josh Trutwin
On Tue, 4 May 2004 09:46:27 -0400 "Tucker, Gabriel" <[EMAIL PROTECTED]> wrote: > Hello All: > > I am having a problem with both V4.0.16 and 4.0.18. Let me explain: > > I have a database with two InnoDB tables in v4.0.16. I backup up > this database every night using the following command: > >

RE: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Marvin Wright
--- From: Tucker, Gabriel [mailto:[EMAIL PROTECTED] Sent: 04 May 2004 15:13 To: Mysql General (E-mail) Subject: RE: InnoDB - Foreign Key - Error 150. Marvin I believe that is the problem with the restore. When I create the archive file using the mysqldump command and options previously listed, I

RE: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Tucker, Gabriel
14:46 To: Mysql General (E-mail) Subject: InnoDB - Foreign Key - Error 150. Hello All: I am having a problem with both V4.0.16 and 4.0.18. Let me explain: I have a database with two InnoDB tables in v4.0.16. I backup up this database every night using the following command: mysqldump

RE: InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Marvin Wright
) Subject: InnoDB - Foreign Key - Error 150. Hello All: I am having a problem with both V4.0.16 and 4.0.18. Let me explain: I have a database with two InnoDB tables in v4.0.16. I backup up this database every night using the following command: mysqldump --allow-keywords --host=$HOST --flush

InnoDB - Foreign Key - Error 150.

2004-05-04 Thread Tucker, Gabriel
Hello All: I am having a problem with both V4.0.16 and 4.0.18. Let me explain: I have a database with two InnoDB tables in v4.0.16. I backup up this database every night using the following command: mysqldump --allow-keywords --host=$HOST --flush-logs --disable-keys --opt --port=$1 -