mirror of
https://github.com/MariaDB/server.git
synced 2025-01-22 06:44:16 +01:00
140b488c96
a too large value": the bug was that if MySQL generated a value for an auto_increment column, based on auto_increment_* variables, and this value was bigger than the column's max possible value, then that max possible value was inserted (after issuing a warning). But this didn't honour auto_increment_* variables (and so could cause conflicts in a master-master replication where one master is supposed to generated only even numbers, and the other only odd numbers), so now we "round down" this max possible value to honour auto_increment_* variables, before inserting it.
12 lines
516 B
Text
12 lines
516 B
Text
#####################################
|
|
# Wrapper for rpl_auto_increment.test#
|
|
#####################################
|
|
########################################################
|
|
# By JBM 2005-02-15 Wrapped to allow reuse of test code#
|
|
# Added to skip if ndb is default #
|
|
########################################################
|
|
-- source include/not_ndb_default.inc
|
|
-- source include/have_innodb.inc
|
|
let $engine_type=innodb;
|
|
let $engine_type2=myisam;
|
|
-- source extra/rpl_tests/rpl_auto_increment.test
|