From: Jorge Bastos
Date: March 30 2006 7:12pm
Subject: Problem with innodb
List-Archive: http://lists.mysql.com/win32/18164
Message-Id: <008801c6542d$e6dad380$0101a8c0@pcjorge>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0085_01C65436.483D6C70"

------=_NextPart_000_0085_01C65436.483D6C70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

People, anyone had this problem descrived below?
http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting-datadict.ht=
ml

InnoDB: Error: table test/parent already exists in InnoDB internal
InnoDB: data dictionary. Have you deleted the .frm file
InnoDB: and not used DROP TABLE? Have you used DROP DATABASE
InnoDB: for InnoDB tables in MySQL version <=3D 3.23.43?
InnoDB: See the Restrictions section of the InnoDB manual.
InnoDB: You can drop the orphaned table inside InnoDB by
InnoDB: creating an InnoDB table with the same name in another
InnoDB: database and moving the .frm file to the current database.
InnoDB: Then MySQL thinks the table exists, and DROP TABLE will
InnoDB: succeed.


I can't create tables with engine=3Dinnodb


Jorge
------=_NextPart_000_0085_01C65436.483D6C70--