Re: MySQL RE: insertion problem !!

2002-02-12 Thread Heikki Tuuri
Chetan, the type of the column user_id is different in your two tables: in the parent table it is UNSIGNED, but signed in the child table. The internal storage format of a signed integer is different from an unsigned integer. That is why adding the child row fails. I changed now InnoDB-3.23.48 s

MySQL RE: insertion problem !!

2002-02-12 Thread Chetan Lavti
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 07, 2002 2:22 PM To: Chetan Lavti Subject: Re: insertion problem !!=20 Your message cannot be posted because it appears to be either spam or simply off topic to our filter. To bypass the filt

FW: MySQL RE: insertion problem !!

2002-02-11 Thread Chetan Lavti
hi, I have two tables as : please concentrate on domain_id and INDEX Create table ls_domain ( domain_id INT(4) UNSIGNED AUTO_INCREMENT , domain_addr VARCHAR(80), domain_name CHAR(50) UNIQUE KEY, domain_port INT(6) UNSIGNED, domain_ip VARCHAR(15), created_by VARCHAR(40), created_date

Re: MySQL RE: insertion problem !!

2002-02-07 Thread Heikki Tuuri
Chetan, the type of the column user_id is different in your two tables: in the parent table it is UNSIGNED, but signed in the child table. The internal storage format of a signed integer is different from an unsigned integer. That is why adding the child row fails. I changed now InnoDB-3.23.48 s

FW: MySQL RE: insertion problem !!

2002-02-07 Thread Chetan Lavti
hi, I have two tables as : please concentrate on domain_id and INDEX Create table ls_domain ( domain_id INT(4) UNSIGNED AUTO_INCREMENT , domain_addr VARCHAR(80), domain_name CHAR(50) UNIQUE KEY, domain_port INT(6) UNSIGNED, domain_ip VARCHAR(15), created_by VARCHAR(40), created_date

MySQL RE: insertion problem !!

2002-02-07 Thread Chetan Lavti
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 07, 2002 2:22 PM To: Chetan Lavti Subject: Re: insertion problem !! Your message cannot be posted because it appears to be either spam or simply off topic to our filter. To bypass the filter