An error occurred fetching the project authors.
  1. 27 Jun, 2007 1 commit
  2. 06 Jul, 2006 1 commit
    • guilhem@mysql.com's avatar
      Fix for BUG#20524 "auto_increment_* not observed when inserting · 140b488c
      guilhem@mysql.com authored
      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.
      140b488c
  3. 16 Feb, 2006 1 commit
  4. 22 Dec, 2005 1 commit
  5. 21 Nov, 2004 1 commit
  6. 15 Sep, 2004 1 commit
    • monty@mishka.local's avatar
      Added options --auto-increment-increment and --auto-increment-offset. · 91ff64e1
      monty@mishka.local authored
      This allows one to setup a master <-> master replication with non conflicting auto-increment series.
      Cleaned up binary log code to make it easyer to add new state variables.
      Added simpler 'upper level' logic for artificial events (events that should not cause cleanups on slave).
      Simplified binary log handling.
      Changed how auto_increment works together with to SET INSERT_ID=# to make it more predictable: Now the inserted rows in a multi-row statement are set independent of the existing rows in the table. (Before only InnoDB did this correctly)
      
      91ff64e1