1. 19 Dec, 2007 1 commit
  2. 15 Dec, 2007 1 commit
  3. 14 Dec, 2007 4 commits
  4. 13 Dec, 2007 14 commits
  5. 12 Dec, 2007 2 commits
  6. 11 Dec, 2007 5 commits
  7. 10 Dec, 2007 8 commits
  8. 09 Dec, 2007 2 commits
  9. 08 Dec, 2007 3 commits
    • igor@olga.mysql.com's avatar
      Merge olga.mysql.com:/home/igor/mysql-5.0-opt · be5485ce
      igor@olga.mysql.com authored
      into  olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug32815
      be5485ce
    • timour/tkatchaounov@lapi.mysql.com's avatar
      Fix for BUG#32694 "NOT NULL table field in a subquery produces invalid results" · 9be915e7
      timour/tkatchaounov@lapi.mysql.com authored
        
      The problem was that when convert_constant_item is called for subqueries,
      this happens when we already started executing the top-level query, and
      the field argument of convert_constant_item pointed to a valid table row.
      In turn convert_constant_item used the field buffer to compute the value
      of its item argument. This copied the item's value into the field,
      and made equalities with outer references always true.
        
      The fix saves/restores the original field's value when it belongs to an
      outer table.
      9be915e7
    • igor@olga.mysql.com's avatar
      Fixed bug #27545. · c04d3727
      igor@olga.mysql.com authored
      Both arguments of the function NAME_CONST must be constant expressions.
      This constraint is checked in the Item_name_const::fix_fields method. 
      Yet if the argument of the function was not a constant expression no
      error message was reported. As a result the client hanged waiting for a
      response.
      Now the function Item_name_const::fix_fields reports an error message
      when any of the additional context conditions imposed on the function
      NAME_CONST is not satisfied. 
      c04d3727