Re: Foreign key bug in InnoDB?

2002-07-16 Thread Heikki Tuuri

Daniel,

are you using a non-latin1 character set?  Have you looked in the error log
mysql.err? What, if anything, did mysqld-max print when it crashed?

From the manual http://www.innodb.com/ibman.html#InnoDB_history:
...
MySQL/InnoDB-3.23.49, February 17, 2002
...
Fixed a bug: if one defined a non-latin1 character set as the default
character set, then definition of foreign key constraints could fail in an
assertion failure in dict0crea.c, reporting an internal error 17.
...

Please upgrade to 4.0.2.

Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com

- Original Message -
From: Kiss Daniel [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, July 16, 2002 10:12 AM
Subject: Foreign key bug in InnoDB?


 Hi,

 I'm using MySQL-Max-4.0.1-alpha on WinNT4SP6 with InnoDB as default
 table type.
 I have a database creation script like this:

 //Section A

 CREATE TABLE AParents (
   Id int unsigned not null auto_increment,
   Parent int unsigned not null,

   primary key (Id),
   index Parent (Parent)
 ) TYPE = InnoDB;


 CREATE TABLE AChildren (
   Id int unsigned not null auto_increment,
   Parent int unsigned not null,

   primary key (Id),
   index Parent (Parent),

   foreign key (Parent) references AParents (Id)
 ) TYPE = InnoDB;

 //Section B

 CREATE TABLE BParents (
   Id int unsigned not null auto_increment,
   Parent int unsigned not null,

   primary key (Id),
   index Parent (Parent)
 ) TYPE = InnoDB;


 CREATE TABLE BChildren (
   Id varchar(13) not null default '',
   Parent int unsigned not null,

   primary key (Id),
   index Parent (Parent),

   foreign key (Parent) references BParents (Id)
 ) TYPE = InnoDB;


 When I run the section A and B in any order, MySQL crashes and InnoDB
 tablespaces go wrong and they cannot be repaired (as I restart MySQL).

 The crash appears when I create the second table with a foreign key
 constraint.

 Do I do something wrong or this is a real bug in InnoDB?

 Thx,
Dani

 --
 http://www.mailbox.hu - Mert levelezni kell...


 -
 Before posting, please check:
http://www.mysql.com/manual.php   (the manual)
http://lists.mysql.com/   (the list archive)

 To request this thread, e-mail [EMAIL PROTECTED]
 To unsubscribe, e-mail
[EMAIL PROTECTED]
 Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php





-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Foreign key bug in InnoDB?

2002-07-16 Thread Victoria Reznichenko

Kiss,
Tuesday, July 16, 2002, 10:11:45 AM, you wrote:

KD I'm using MySQL-Max-4.0.1-alpha on WinNT4SP6 with InnoDB as default
KD table type.
KD I have a database creation script like this:

[skip]

KD When I run the section A and B in any order, MySQL crashes and InnoDB
KD tablespaces go wrong and they cannot be repaired (as I restart MySQL).

KD The crash appears when I create the second table with a foreign key
KD constraint.

KD Do I do something wrong or this is a real bug in InnoDB?

Do you use other than latin1 default character set? If so, this bug
was fixed in 3.23.49:
 http://www.innodb.com/ibman.html




-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Victoria Reznichenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   ___/   www.mysql.com




-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Re: Foreign key bug in InnoDB?

2002-07-16 Thread Kiss Daniel

Heikki,

Yes, I'm using Hungarian character-set as default.
I've checked the mysql.err, and it contains nothing important.
The full content of mysql.err right after starting mysqld-max, runnig
the script and crash:

---
MySql: ready for connections
---

Maybe, because MySQL crashed before it could write in the log file.

Anyway, the Hungarian sort order is not proper. And I think it never
will be the way of using those charset conf files. It's much more
difficult than just comparing characters. Sometimes you have to compare
two chars, or there is some chars that have the same value althought
they are different. :-) Will it be realy good any time???

Thx,
   niel

--
http://www.mailbox.hu - Mert levelezni kell...


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php