I installed a fresh copy mySQL-4.1alpha on XP. I ran
it standalone as follows:
mysqld-max --standalone --console
--default-table-type=innodb
I get the same results with my script.
Since I didn't specify a character set, I assume it is
the default (ISO-8859-1) set as specified in the
Section
At 15:59 +0300 9/28/03, Victoria Reznichenko wrote:
Ed Smith [EMAIL PROTECTED] wrote:
Greetings. When I execute the SQL script below in
mySQL 4.1, I get
ERROR 1216: Cannot add or update a child row: a
foreign key constraint fails
It is, of course, choking on the enroll row insert.
Why is
Ed Smith [EMAIL PROTECTED] wrote:
Greetings. When I execute the SQL script below in
mySQL 4.1, I get
ERROR 1216: Cannot add or update a child row: a
foreign key constraint fails
It is, of course, choking on the enroll row insert.
Why is this happening? Here are some things that make
Greetings. When I execute the SQL script below in
mySQL 4.1, I get
ERROR 1216: Cannot add or update a child row: a
foreign key constraint fails
It is, of course, choking on the enroll row insert.
Why is this happening? Here are some things that make
the problem go away:
1. Take out the name
IMO, this is a bug in mySQL. It's fine to convert to
fixed to variable length under the hood; however, it
should not impact implementation.
What's the best work around for this feature? It
looks like I will be forced to change my enroll to use
VARCHAR. I shouldn't have to do this to make it
# [EMAIL PROTECTED] / 2003-09-26 15:12:03 -0700:
--- Harald Fuchs [EMAIL PROTECTED] wrote:
Ed Smith [EMAIL PROTECTED] writes:
Greetings. When I execute the SQL script below in
mySQL 4.1, I get
ERROR 1216: Cannot add or update a child row: a foreign key
constraint fails
It
Hi,
- Original Message -
From: Roman Neuhauser
Sent: Friday, September 26, 2003 6:05 PM
Subject: Re: FOREIGN KEY Weirdness in mySQL 4.1 with VARCHAR
# [EMAIL PROTECTED] / 2003-09-26 15:12:03 -0700:
--- Harald Fuchs [EMAIL PROTECTED] wrote:
Ed Smith [EMAIL PROTECTED] writes