…AUTO_INCREMENT to be based off the maximum value across all tables, respecting AUTO_INCREMENT set for the Merge Table itself. Neither of these expectations really true: mysql> create table a1(i int unsigned not null auto_increment primary key); Query…
Post: Edge-case behavior of INSERT...ODKU
…PRIMARY KEY is always going to be considered as being defined first. So, MySQL checks our INSERT, sees that the next auto-inc value…maximum value for an auto-increment…
Post: Innodb row size limitation
… NOT NULL AUTO_INCREMENT, fname TEXT…PRIMARY KEY (id) ) Engine=InnoDB; Now you insert some test data into it: mysql> INSERT INTO example -> VALUES…Query OK, 1 row affected (0.03 sec) All goes ok. Now you begin using this structure in production, and ocassionally get…fields’ maximum allowed value. …

