• kroki/tomash@moonlight.intranet's avatar
    BUG#21726: Incorrect result with multiple invocations of LAST_INSERT_ID. · ee0cebf9
    kroki/tomash@moonlight.intranet authored
    Note: bug#21726 does not directly apply to 4.1, as it doesn't have stored
    procedures.  However, 4.1 had some bugs that were fixed in 5.0 by the
    patch for bug#21726, and this patch is a backport of those fixes.
    Namely, in 4.1 it fixes:
    
      - LAST_INSERT_ID(expr) didn't return value of expr (4.1 specific).
    
      - LAST_INSERT_ID() could return the value generated by current
        statement if the call happens after the generation, like in
    
          CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT);
          INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());
    
      - Redundant binary log LAST_INSERT_ID_EVENTs could be generated.
    ee0cebf9
log_event.cc 95.9 KB