1. 26 Jan, 2007 1 commit
    • 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
  2. 22 Jan, 2007 1 commit
  3. 13 Jan, 2007 1 commit
  4. 11 Jan, 2007 3 commits
    • evgen@moonbone.local's avatar
      Bug#23409: Arguments of the ENCODE() and the DECODE() functions were not printed · fc0e206c
      evgen@moonbone.local authored
      correctly.
      
      The Item_func::print method was used to print the Item_func_encode and the
      Item_func_decode objects. The last argument to ENCODE and DECODE functions
      is a plain C string and thus Item_func::print wasn't able to print it.
      
      The print() method is added to the Item_func_encode class. It correctly
      prints the Item_func_encode and the Item_func_decode objects.
      fc0e206c
    • evgen@moonbone.local's avatar
      Merge fix for bug#17711 · f35e10d4
      evgen@moonbone.local authored
      f35e10d4
    • evgen@moonbone.local's avatar
      Bug#17711: DELETE doesn't use index when ORDER BY, LIMIT and non-restricting · c17bf5cb
      evgen@moonbone.local authored
      WHERE is present.
      
      If a DELETE statement with ORDER BY and LIMIT contains a WHERE clause
      with conditions that for sure cannot be used for index access (like in
      WHERE @var:= field) the execution always follows the filesort path.    
      It happens currently even when for the above case there is an index that
      can be used to speedup sorting by the order by list.
      
      Now if a DELETE statement with ORDER BY and LIMIT contains such WHERE
      clause conditions that cannot be used to build any quick select then
      the mysql_delete() tries to use an index like there is no WHERE clause at all.
      c17bf5cb
  5. 10 Jan, 2007 3 commits
  6. 03 Jan, 2007 1 commit
  7. 02 Jan, 2007 4 commits
  8. 31 Dec, 2006 1 commit
  9. 25 Dec, 2006 1 commit
  10. 20 Dec, 2006 2 commits
    • istruewing@chilla.local's avatar
      Bug#25213 - Compiler warnings in MyISAM code · d9b9778e
      istruewing@chilla.local authored
      Compiler warnings due to non-matching conversion
      specifications in format strings in DBUG_PRINT calls,
      due to non-used parameters (in non-debug mode), and
      due to seemingly uninitialized variables.
      
      Initialized variables, declared parameters unused, and
      casted DBUG_PRINT arguments to get rid of warnings.
      d9b9778e
    • istruewing@chilla.local's avatar
      Bug#25208 - Warnings in mi_packrec.c · 1d69857c
      istruewing@chilla.local authored
      Compiler warnings due to non-matching conversion
      specifications in format strings in DBUG_PRINT calls.
      
      Fixed DBUG_PRINT format specifiactions.
      1d69857c
  11. 19 Dec, 2006 1 commit
  12. 14 Dec, 2006 3 commits
  13. 13 Dec, 2006 1 commit
  14. 12 Dec, 2006 1 commit
  15. 11 Dec, 2006 2 commits
  16. 08 Dec, 2006 2 commits
  17. 07 Dec, 2006 3 commits
  18. 06 Dec, 2006 2 commits
  19. 05 Dec, 2006 6 commits
  20. 04 Dec, 2006 1 commit