Re: Error/crash with InnoDB if table name = database name - Miguel Angel Solórzano - com.mysql.lists.bugs

2 messages in com.mysql.lists.bugsRe: Error/crash with InnoDB if table ...

From	Sent On	Attachments
Miguel Angel Solórzano	20 Jun 2001 12:30
Heikki Tuuri	21 Jun 2001 08:17

Subject:	Re: Error/crash with InnoDB if table name = database name
From:	Miguel Angel Solórzano (mig...@mysql.com)
Date:	06/20/2001 12:30:40 PM
List:	com.mysql.lists.bugs

At 20:41 20/06/2001 +0200, Markus Wichitill wrote: Hi,

Thanks for the bug report. I was be able to repeat the issue after I dropped the already existing database test. The problem is InnoDB applies the following error:

Innobase: error: table test/test already exists in Innobase data dictionary

The above should be analyzed by Heikki.

Regards, Miguel

Hi,

I'm using MySQL 3.23.39-log compiled from sources on SuSE Linux 6.4. When I create an InnoDB table with the same name as the database, I get the following error message:

mysql> create database test; Query OK, 1 row affected (0.01 sec)

mysql> create table test (x int) type=innodb; ERROR 1005: Can't create table './test/test.frm' (errno: 0)

Creating an InnoDB table with a different name works fine, as does creating a MyISAM table with the same name:

mysql> create table test2 (x int) type=innodb; Query OK, 0 rows affected (0.01 sec)

mysql> create table test (x int); Query OK, 0 rows affected (0.00 sec)

When I try to convert the MyISAM table to InnoDB, the server crashes and the table is lost:

mysql> alter table test type = innodb; ERROR 2013: Lost connection to MySQL server during query

I could provide additional information and maybe a stacktrace if necessary, but I'd prefer not to recompile the server etc. in case this problem is already known or easy to fix without.

To request this thread, e-mail <mysq...@lists.mysql.com> To unsubscribe, e-mail <mysql-unsubscribe-solorzano=inte...@lists.mysql.com> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php