Michael, > InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB > InnoDB: data dictionary, but has one in MySQL!
these messages below derive from this bug fix: " MySQL/InnoDB-3.23.54, December 12, 2002 ... Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL. ... " If you have not defined a PRIMARY KEY, MySQL internally treats the first UNIQUE KEY with all non-NULL columns as the primary key. That can cause confusion between InnoDB and MySQL. I am not sure if it can cause any serious errors. Fix: drop and recreate the tables below. In 3.23.54 MySQL and InnoDB are harmonized. Hmm... I have to add this advice to the error printout. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query ..................................... Subject: Weird errors appearing in log.. From: Michael Bacarella Date: Thu, 19 Dec 2002 14:17:19 -0500 ---------------------------------------------------------------------------- ---- I upgraded a very high load site from 3.23.51 to 3.23.54a. The upgrade seems to have gone fine, but some really odd messages appeared in the error log: InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/Pilot has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/EmailCache has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/RecentMatches has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/EmailCache has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! InnoDB: Error: table ./m4m4sex/RecentMatches has no primary key in InnoDB InnoDB: data dictionary, but has one in MySQL! They stopped after the first minute or two. Is this cause for concern? How can I make them go away? :) -- Michael Bacarella | Netgraft Corp | 545 Eighth Ave #401 Systems Analysis | New York, NY 10018 Technical Support | 212 946-1038 | 917 670-6982 Managed Services | http://netgraft.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
