1. 19 Apr, 2007 2 commits
  2. 18 Apr, 2007 3 commits
  3. 13 Apr, 2007 1 commit
    • svoj@mysql.com/june.mysql.com's avatar
      BUG#27516 - divide by zero crash during optimize table · ed81a81a
      svoj@mysql.com/june.mysql.com authored
      When a table status is requested by statement like SHOW TABLE
      STATUS and there is another statement (e.g. DELETE) sets
      number of records to 0 concurrently, we may get division by
      zero error, which crashes a server.
      
      This is fixed by using thread local variable x->records instead
      of shared info->state->records when we check if it is zero and
      divide by it.
      ed81a81a
  4. 12 Apr, 2007 1 commit
  5. 10 Apr, 2007 1 commit
    • svoj@mysql.com/april.(none)'s avatar
      BUG#24342 - Incorrect results with query over MERGE table · bcbcacb8
      svoj@mysql.com/april.(none) authored
      MERGE engine may return incorrect values when several representations
      of equal keys are present in the index. For example "groß" and "gross"
      or "gross" and "gross " (trailing space), which are considered equal,
      but have different lengths.
      
      The problem was that key length was not recalculated after key lookup.
      
      Only MERGE engine is affected.
      bcbcacb8
  6. 08 Apr, 2007 1 commit
  7. 06 Apr, 2007 4 commits
  8. 05 Apr, 2007 11 commits
  9. 04 Apr, 2007 3 commits
    • tomas@whalegate.ndb.mysql.com's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.0 · 881fd531
      tomas@whalegate.ndb.mysql.com authored
      into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
      881fd531
    • mskold/marty@mysql.com/linux.site's avatar
      Bug #26242 UPDATE with subquery and triggers failing with cluster tables · 625a2629
      mskold/marty@mysql.com/linux.site authored
      In certain cases AFTER UPDATE/DELETE triggers on NDB tables that referenced
      subject table didn't see the results of operation which caused invocation
      of those triggers. In other words AFTER trigger invoked as result of update
      (or deletion) of particular row saw version of this row before update (or
      deletion).
      
      The problem occured because NDB handler in those cases postponed actual
      update/delete operations to be able to perform them later as one batch.
      
      This fix solves the problem by disabling this optimization for particular
      operation if subject table has AFTER trigger for this operation defined.
      To achieve this we introduce two new flags for handler::extra() method:
      HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH.
      These are called if there exists AFTER DELETE/UPDATE triggers during a
      statement that potentially can generate calls to delete_row()/update_row().
      This includes multi_delete/multi_update statements as well as insert statements
      that do delete/update as part of an ON DUPLICATE statement.
      625a2629
    • tsmith@quadxeon.mysql.com's avatar
      Merge tsmith@bk-internal.mysql.com:/home/bk/mysql-5.0 · ab15c0fb
      tsmith@quadxeon.mysql.com authored
      into  quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/mrg04/50
      ab15c0fb
  10. 03 Apr, 2007 3 commits
  11. 02 Apr, 2007 10 commits