Description:
i belive that mysqldump --skip-opt dumping breaks table definitions:
an example:
# mysql --version
mysql Ver 14.7 Distrib 4.1.21, for pc-linux-gnu (i686) using readline 4.3
# mysqldump -d db
-- MySQL dump 10.9
--
-- Host: localhost Database: spletkar
-- ------------------------------------------------------
-- Server version 4.1.21-standard-log
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `cms_phpwcms_address`
--
DROP TABLE IF EXISTS `cms_phpwcms_address`;
CREATE TABLE `cms_phpwcms_address` (
`address_id` int(11) NOT NULL auto_increment,
`address_key` varchar(255) NOT NULL default '',
`address_email` varchar(255) NOT NULL default '',
`address_name` text NOT NULL,
`address_verified` int(1) NOT NULL default '0',
`address_tstamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
`address_subscription` blob NOT NULL,
PRIMARY KEY (`address_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
...
# mysqldump --skip-opt -d db
-- MySQL dump 10.9
--
-- Host: localhost Database: spletkar
-- ------------------------------------------------------
-- Server version 4.1.21-standard-log
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `cms_phpwcms_address`
--
CREATE TABLE `cms_phpwcms_address` (
`address_id` int(11) NOT NULL,
`address_key` varchar(255) NOT NULL default '',
`address_email` varchar(255) NOT NULL default '',
`address_name` text NOT NULL,
`address_verified` int(1) NOT NULL default '0',
`address_tstamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
`address_subscription` blob NOT NULL,
PRIMARY KEY (`address_id`)
);
...
and almost the same on a different box
# mysql --version
mysql Ver 14.12 Distrib 5.0.22, for redhat-linux-gnu (i386) using readline 5.0
# mysqldump -d db
...
CREATE TABLE `phpwcms_guestbook` (
`guestbook_id` int(11) NOT NULL auto_increment,
`guestbook_cid` int(11) NOT NULL default '0',
...
# mysqldump --skip-opt -d db
...
CREATE TABLE `phpwcms_guestbook` (
`guestbook_id` int(11) NOT NULL,
`guestbook_cid` int(11) NOT NULL default '0',
...
How to repeat:
mysqldump --opt -dA | grep -ci 'auto_increment'
mysqldump --skip-opt -dA | grep -ci 'auto_increment'
and see if the numbers match
Suggested fix:
don't use --skip-opt :)
