1. 15 Jun, 2007 1 commit
    • igor@olga.mysql.com's avatar
      Fixed bug #27932: the function LOCATE returned NULL if any · 0f0d4720
      igor@olga.mysql.com authored
      of its arguments was evaluated to NULL, while the predicate
      LOCATE(str,NULL) IS NULL erroneously was evaluated to FALSE.
      
      This happened because the Item_func_locate::fix_length_and_dec
      method by mistake set the value of the maybe_null flag for 
      the function item to 0. In consequence of this the function 
      was considered as the one that could not ever return NULL.
      0f0d4720
  2. 14 Jun, 2007 5 commits
  3. 13 Jun, 2007 1 commit
    • igor@olga.mysql.com's avatar
      Fixed bug #28980: the result of ROUND(<decimal expr>,<int column>) · 20ad5150
      igor@olga.mysql.com authored
      was erroneously converted to double, while the result of
      ROUND(<decimal expr>, <int literal>) was preserved as decimal.
      As a result of such a conversion the value of ROUND(D,A) could
      differ from the value of ROUND(D,val(A)) if D was a decimal expression.
      
      Now the result of the ROUND function is never converted to 
      double if the first argument is decimal.  
      20ad5150
  4. 12 Jun, 2007 5 commits
  5. 11 Jun, 2007 1 commit
    • evgen@moonbone.local's avatar
      Bug#28904: INSERT .. ON DUPLICATE was silently updating rows when it shouldn't. · 4cdbe25a
      evgen@moonbone.local authored
      When the INSERT .. ON DUPLICATE KEY UPDATE has to update a matched row but
      the new data is the same as in the record then it returns as if
      no rows were inserted or updated. Nevertheless the row is silently
      updated. This leads to a situation when zero updated rows are reported 
      in the case when data has actually been changed.
      
      Now the write_record function updates a row only if new data differs from
      that in the record.
      4cdbe25a
  6. 09 Jun, 2007 7 commits
  7. 08 Jun, 2007 5 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
    • igor@olga.mysql.com's avatar
      Merge olga.mysql.com:/home/igor/mysql-5.0-opt · e2e672b5
      igor@olga.mysql.com authored
      into  olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug28811
      e2e672b5
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #28754: RPM builds differ from tar.gz in "ALTER ... RENAME" on views · d12fbdd8
      gkodinov/kgeorge@magare.gmz authored
       When constructing the path to the original .frm file ALTER .. RENAME
       was unnecessary (and incorrectly) lowercasing the whole path when not 
       on a case-insensitive filesystem.
       This path should not be modified because of lower_case_table_names
       as it is already in the correct case according to that setting.
       Fixed by removing the lowercasing.
       Unfortunately testing this would require running the tests on a case
       sensitive filesystem in a directory that has uppercase letters.
       This cannot be guaranteed in all setups so no test case added.
      d12fbdd8
    • gluh@mysql.com/eagle.(none)'s avatar
      Bug#18660 Can't grant any privileges on single table in database with underscore char · a809813b
      gluh@mysql.com/eagle.(none) authored
      In case of database level grant the database name may be a pattern,
      in case of table|column level grant the database name can not be a pattern.
      We use 'dont_check_global_grants' as a flag to determine
      if it's database level grant command 
      (see SQLCOM_GRANT case, mysql_execute_command() function) and
      set db_is_pattern according to 'dont_check_global_grants' value.
      a809813b
    • 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
  8. 07 Jun, 2007 10 commits
  9. 06 Jun, 2007 5 commits