1. 21 Jul, 2005 2 commits
  2. 20 Jul, 2005 7 commits
  3. 19 Jul, 2005 10 commits
  4. 18 Jul, 2005 7 commits
  5. 17 Jul, 2005 2 commits
  6. 16 Jul, 2005 4 commits
    • timour@mysql.com's avatar
      Added test for Bug #11521 · ff0c7f22
      timour@mysql.com authored
      "Negative integer keys incorrectly substituted for 0 during range analysis."
      
      The problem is that the range optimizer incorrectly replaces any negative
      constant with '0' for all types except BIGINT because the method save_in_field()
      casts negative integers to non-negative. This causes incorrect query
      results where (0 = any_negative_number).
      
      The problem caused by this bug is fixed by the patch for BUG#11185.
      That patch constitutes an optimization due to which the problem code is
      never called with negative constants. This patch adds a test so we are sure
      that the problem does not reappear.
      ff0c7f22
    • jimw@mysql.com's avatar
      Merge bk-internal:/home/bk/mysql-4.1 · c61ce0d9
      jimw@mysql.com authored
      into  mysql.com:/home/jimw/my/mysql-4.1-clean
      c61ce0d9
    • evgen@moonbone.local's avatar
      Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-4.1 · 52569ad5
      evgen@moonbone.local authored
      into moonbone.local:/work/mysql-4.1-bug-11868
      52569ad5
    • evgen@moonbone.local's avatar
      Fix bug#11868 NOT NULL ref optimization in subquery used in update must be · 81d93df1
      evgen@moonbone.local authored
      disabled if ref is built with a key from the updated table
      
      Problem was in add_not_null_conds() optimization function.
      It contains following code:
      JOIN_TAB *referred_tab= not_null_item->field->table->reginfo.join_tab;
      ...
      add_cond_and_fix(&referred_tab->select_cond, notnull);
      For UPDATE described in bug report referred_tab is 0 and dereferencing it
      crashes the server.
      81d93df1
  7. 15 Jul, 2005 8 commits