Bug #54898 MySQL Workbench- allow ignore of auto increment values
Submitted: 29 Jun 2010 16:59 Modified: 9 Jan 2015 10:30
Reporter: Pamela Goloskie Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S4 (Feature request)
Version:5.2.22 OS:Any
Assigned to: CPU Architecture:Any

[29 Jun 2010 16:59] Pamela Goloskie
Description:
When doing a synchronize model or catalog diff report, it would be helpful to have an option to ignore the next auto increment value.  
For instance, when doing a compare between staging and production, I would expect the values to be different. It would make the report more useful and easier to work with if these messages could be suppressed:

Table `foo`.`foo_bar` was modified
  attributes:
  - next auto increment: 184 --> 1522

How to repeat:
Create same table in two different schemas, identical except for value of auto increment. Do a synchronize model . 

In schema 1:
CREATE TABLE `notifications_log` (
  `msgid` int(11) NOT NULL AUTO_INCREMENT,
  `type` varchar(25) DEFAULT NULL,
  `sender` varchar(100) DEFAULT NULL,
  `targets` varchar(50) DEFAULT NULL,
  `icon` varchar(50) DEFAULT NULL,
  `txt` text,
  `postdate` datetime DEFAULT NULL,
  `expires` datetime DEFAULT NULL,
  PRIMARY KEY (`msgid`)
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8$$

ALTER TABLE `notifications_log`AUTO_INCREMENT=1234;

********************************************************
In Schema 2

CREATE TABLE `notifications_log` (
  `msgid` int(11) NOT NULL AUTO_INCREMENT,
  `type` varchar(25) DEFAULT NULL,
  `sender` varchar(100) DEFAULT NULL,
  `targets` varchar(50) DEFAULT NULL,
  `icon` varchar(50) DEFAULT NULL,
  `txt` text,
  `postdate` datetime DEFAULT NULL,
  `expires` datetime DEFAULT NULL,
  PRIMARY KEY (`msgid`)
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8$$

ALTER TABLE `notifications_log`AUTO_INCREMENT=1234;

Suggested fix:
Allow an option to ignore next value in auto increment while doing model synchronization.
[29 Jun 2010 17:44] Pamela Goloskie
second update should be different value, sorry

ALTER TABLE `notifications_log`AUTO_INCREMENT=5555;
[6 Jul 2010 15:50] Alfredo Kojima
Thank you for the feature suggestion.