1. 11 Jun, 2007 2 commits
  2. 10 Jun, 2007 1 commit
  3. 09 Jun, 2007 3 commits
  4. 08 Jun, 2007 3 commits
    • holyfoot/hf@mysql.com/hfmain.(none)'s avatar
      Bug #28333 Test "flush" tries to create a new thread - on only one platform · 96d07631
      holyfoot/hf@mysql.com/hfmain.(none) authored
      on PPC/Debian Linux default stack size for a thread is too big.
      As we use default thread settings in mysqltest, the
      thread creation fails if we create lots of threads (as it
      happens in flush.test). So now stack size is explicitly specified
      for the mysqltest
      96d07631
    • gluh@mysql.com/eagle.(none)'s avatar
      Bug#27684 undocumented difference between SHOW ENGINES and I_S.ENGINES · 237374c4
      gluh@mysql.com/eagle.(none) authored
      Changed SHOW ENGINES to work in the same way as I_S.ENGINES.
      For this: removed the functions mysqld_show_storage_engines and show_handlerton, and
      made SHOW ENGINES work via the common function iter_schema_engines.
      There in no test case because an engine (except of MyISAM) may be not compiled or disabled
      which may affect the test result.
      237374c4
    • igor@olga.mysql.com's avatar
      Fixed bug #28811: crash for a query containing a subquery with · 2d29a57f
      igor@olga.mysql.com authored
      ORDER BY and LIMIT 1. 
      The bug was introduced by the patch for bug 21727. The patch
      erroneously skipped initialization of the array of headers
      for sorted records for non-first evaluations of the subquery.
      
      To fix the problem a new parameter has been added to the
      function make_char_array that performs the initialization.
      Now this function is called for any invocation of the 
      filesort procedure. Yet it allocates the buffer for sorted
      records only if this parameter is NULL.
      2d29a57f
  5. 07 Jun, 2007 8 commits
  6. 06 Jun, 2007 7 commits
  7. 05 Jun, 2007 3 commits
    • evgen@moonbone.local's avatar
      Bug#28778: Wrong result of BETWEEN when comparing a DATETIME field with an · 0a91c7cc
      evgen@moonbone.local authored
      integer constants.
      
      This bug is introduced by the fix for bug#16377. Before the fix the 
      Item_func_between::fix_length_and_dec method converted the second and third
      arguments to the type of the first argument if they were constant and the first
      argument is of the DATE/DATETIME type. That approach worked well for integer
      constants and sometimes produced bad result for string constants. The fix for
      the bug#16377 wrongly removed that code at all and as a result of this the
      comparison of a DATETIME field and an integer constant was carried out in a
      wrong way and sometimes led to wrong result sets.
      
      Now the Item_func_between::fix_length_and_dec method converts the second and
      third arguments to the type of the first argument if they are constant, the
      first argument is of the DATE/DATETIME type and the DATETIME comparator isn't
      applicable.
      0a91c7cc
    • holyfoot/hf@hfmain.(none)'s avatar
      Merge bk@192.168.21.1:mysql-5.1-opt · c571b6e0
      holyfoot/hf@hfmain.(none) authored
      into  mysql.com:/home/hf/work/28477/my51-28477
      c571b6e0
    • gkodinov/kgeorge@magare.gmz's avatar
      Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.1-opt · 0c0201c9
      gkodinov/kgeorge@magare.gmz authored
      into  magare.gmz:/home/kgeorge/mysql/autopush/B28488-5.1-opt
      0c0201c9
  8. 04 Jun, 2007 7 commits
  9. 03 Jun, 2007 6 commits