1. 23 Jun, 2005 6 commits
    • timour@mysql.com's avatar
      Merge tkatchaounov@bk-internal.mysql.com:/home/bk/mysql-4.1 · 9dca446d
      timour@mysql.com authored
      into mysql.com:/home/timka/mysql/src/4.1-virgin
      9dca446d
    • lenz@mysql.com's avatar
      Merge lgrimmer@bk-internal.mysql.com:/home/bk/mysql-4.1 · a5e8bce1
      lenz@mysql.com authored
      into mysql.com:/space/my/mysql-4.1
      a5e8bce1
    • lenz@mysql.com's avatar
      - manual merge of the new node names · cacb7199
      lenz@mysql.com authored
      cacb7199
    • lenz@mysql.com's avatar
    • timour@mysql.com's avatar
      Merge mysql.com:/home/timka/mysql/src/4.1-virgin · 3589c51c
      timour@mysql.com authored
      into mysql.com:/home/timka/mysql/src/4.1-bug-11185
      3589c51c
    • timour@mysql.com's avatar
      Fix for BUG#11185. · 294498e2
      timour@mysql.com authored
      The source of the problem is in Field_longlong::cmp. If 'this' is
      an unsigned number, the method casts both the current value, and
      the constant that we compare with to an unsigned number. As a
      result if the constant we compare with is a negative number, it
      wraps to some unsigned number, and the comparison is incorrect.
      
      When the optimizer chooses the "range" access method, this problem
      causes handler::read_range_next to reject the current key when the
      upper bound key is a negative number because handler::compare_key
      incorrectly considers the positive and negative keys to be equal.
      
      The current patch does not correct the source of the problem in
      Field_longlong::cmp because it is not easy to propagate sign
      information about the constant at query execution time. Instead
      the patch changes the range optimizer so that it never compares
      unsiged fields with negative constants. As an added benefit,
      queries that do such comparisons will execute faster because
      the range optimizer replaces conditions like:
      (a) (unsigned_int [< | <=] negative_constant) == FALSE
      (b) (unsigned_int [> | >=] negative_constant) == TRUE
      with the corresponding constants.
      In some cases this may even result in constant time execution.
      294498e2
  2. 22 Jun, 2005 10 commits
  3. 21 Jun, 2005 12 commits
  4. 20 Jun, 2005 12 commits