1. 14 May, 2007 1 commit
  2. 10 May, 2007 1 commit
  3. 08 May, 2007 1 commit
  4. 07 May, 2007 1 commit
  5. 04 May, 2007 2 commits
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #27531: the 4.1 fix. · d11e1f24
      gkodinov/kgeorge@magare.gmz authored
      When checking for applicability of join cache
      we must disable its usage only if there is no
      temp table in use.
      When a temp table is used we can use join
      cache (and it will not make the result-set 
      unordered) to fill the temp table. The filesort() 
      operation is then applied to the data in the temp 
      table and hence is not affected by join cache
      usage.
      Fixed by narrowing the condition for disabling 
      join cache to exclude the case where temp table
      is used.
      d11e1f24
    • df@pippilotta.erinye.com's avatar
      Merge pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build · 1eaf5936
      df@pippilotta.erinye.com authored
      into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build-work
      1eaf5936
  6. 03 May, 2007 1 commit
    • evgen@moonbone.local's avatar
      Bug#23656: Wrong conversion result of a DATETIME to integer using CAST function. · 7f9411c1
      evgen@moonbone.local authored
      The generic string to int conversion was used by the Item_func_signed and
      the Item_func_unsigned classes to convert DATE/DATETIME values to the
      SIGNED/UNSIGNED type. But this conversion produces wrong results for such
      values.
      
      Now if the item which result has to be converted can return its result as
      longlong then the item->val_int() method is used to allow the item to carry
      out the conversion itself and return the correct result.
      This condition is checked in the Item_func_signed::val_int() and the
      Item_func_unsigned::val_int() functions.
      7f9411c1
  7. 02 May, 2007 2 commits
  8. 30 Apr, 2007 1 commit
  9. 29 Apr, 2007 5 commits
  10. 28 Apr, 2007 3 commits
    • gshchepa/uchum@gshchepa.loc's avatar
      Fixed bug #13191. · 3adcb94e
      gshchepa/uchum@gshchepa.loc authored
      INSERT...ON DUPLICATE KEY UPDATE may cause error 1032: 
      "Can't find record in ..." if we are inserting into
      InnoDB table unique index of partial key with
      underlying UTF-8 string field.
      
      This error occurs because INSERT...ON DUPLICATE uses a wrong
      procedure to copy string fields of multi-byte character sets
      for index search.
      3adcb94e
    • gshchepa/uchum@gshchepa.loc's avatar
      Fixed bug #20710. · 3322b3c0
      gshchepa/uchum@gshchepa.loc authored
      This bug occurs when error message length exceeds allowed limit: my_error()
      function outputs "%s" sequences instead of long string arguments.
      
      Formats like %-.64s are very common in errmsg.txt files, however my_error()
      function simply ignores precision of those formats.
      3322b3c0
    • df@pippilotta.erinye.com's avatar
      Merge pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build · d7690722
      df@pippilotta.erinye.com authored
      into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-4.1-build-work
      d7690722
  11. 27 Apr, 2007 1 commit
  12. 26 Apr, 2007 2 commits
  13. 24 Apr, 2007 3 commits
  14. 23 Apr, 2007 2 commits
  15. 20 Apr, 2007 2 commits
  16. 19 Apr, 2007 1 commit
  17. 18 Apr, 2007 1 commit
  18. 17 Apr, 2007 4 commits
  19. 14 Apr, 2007 1 commit
  20. 12 Apr, 2007 2 commits
  21. 11 Apr, 2007 3 commits