1. 09 Feb, 2007 1 commit
  2. 08 Feb, 2007 1 commit
  3. 07 Feb, 2007 2 commits
  4. 05 Feb, 2007 1 commit
  5. 02 Feb, 2007 5 commits
  6. 01 Feb, 2007 5 commits
  7. 31 Jan, 2007 2 commits
  8. 30 Jan, 2007 4 commits
  9. 29 Jan, 2007 1 commit
  10. 26 Jan, 2007 2 commits
    • gluh@mysql.com/eagle.(none)'s avatar
      Merge mysql.com:/home/gluh/MySQL/Merge/4.1-opt · 658777d8
      gluh@mysql.com/eagle.(none) authored
      into  mysql.com:/home/gluh/MySQL/Merge/4.1
      658777d8
    • igor@olga.mysql.com's avatar
      Fixed bug #24653. · 36df33d8
      igor@olga.mysql.com authored
      The bug report has demonstrated the following two problems.
      1. If an ORDER/GROUP BY list includes a constant expression being 
      optimized away and, at the same time, containing single-row
      subselects that return more that one row, no error is reported.
      Strictly speaking the standard allows to ignore error in this case.
      Yet, now a corresponding fatal error is reported in this case.
      2. If a query requires sorting by expressions containing single-row
      subselects that, however, return more than one row, then the execution
      of the query may cause a server crash. 
      To fix this some code has been added that blocks execution of a subselect
      item in case of a fatal error in the method Item_subselect::exec.
      36df33d8
  11. 25 Jan, 2007 1 commit
  12. 24 Jan, 2007 6 commits
  13. 23 Jan, 2007 2 commits
  14. 22 Jan, 2007 7 commits