An error occurred fetching the project authors.
  1. 01 Sep, 2005 1 commit
  2. 31 Aug, 2005 1 commit
  3. 29 Aug, 2005 1 commit
  4. 15 Aug, 2005 1 commit
  5. 13 Aug, 2005 1 commit
    • tsmith@.mysql.com's avatar
      sql_parse.cc: · 9097bd2f
      tsmith@.mysql.com authored
        Don't skip SET command even if --replicate-wild* says to.
        E.g., SET ONE_SHOT TIME_ZONE = 'XYZ' should be executed (BUG #12542)
      9097bd2f
  6. 08 Aug, 2005 1 commit
    • monty@mysql.com's avatar
      Review of new pushed code · 99cb0835
      monty@mysql.com authored
      - Fixed some error condtion when handling dates with 'T'
      - Added extra test for bug #11867 (Wrong result with "... WHERE ROW( a, b ) IN ( SELECT DISTINCT a, b WHERE ...)" to show it's not yet fixed
      - Safety fixes and cleanups
      99cb0835
  7. 07 Aug, 2005 1 commit
    • acurtis@xiphis.org's avatar
      Bug#10109 · 015447b2
      acurtis@xiphis.org authored
        "INSERT .. SELECT ... ON DUPLICATE KEY UPDATE fails"
        Ensure that check_insert_fields() is only called once when
        doing an INSERT..SELECT
      015447b2
  8. 05 Aug, 2005 1 commit
  9. 25 Jul, 2005 1 commit
  10. 23 Jul, 2005 1 commit
  11. 13 Jul, 2005 1 commit
    • konstantin@mysql.com's avatar
      - a fix for Bug#11458 "Prepared statement with subselects return random · bef558b7
      konstantin@mysql.com authored
      data": remove the fix for another bug (8807) that
      added OUTER_REF_TABLE_BIT to all subqueries that used a placeholder
      to prevent their evaluation at prepare. As this bit hanged in 
      Item_subselect::used_tables_cache for ever, a constant subquery with
      a placeholder was never evaluated as such, which caused wrong 
      choice of the execution plan for the statement.
      - to fix Bug#8807 backport a better fix from 5.0
      - post-review fixes.
      bef558b7
  12. 28 Jun, 2005 2 commits
  13. 27 Jun, 2005 2 commits
    • monty@mishka.local's avatar
      Portability fixes · 7398252d
      monty@mishka.local authored
      Fixes while reviewing new pushed code
      NULL as argument to encrypt/decrypt should return NULL without a warning
      7398252d
    • monty@mishka.local's avatar
      Better bug fix for: · 83f90e06
      monty@mishka.local authored
      #9728  'Decreased functionality in "on duplicate key update
      #8147  'a column proclaimed ambigous in INSERT ... SELECT .. ON DUPLICATE'
      
      This ensures fields are uniquely qualified and also that one can't update other tables in the ON DUPLICATE KEY UPDATE part
      83f90e06
  14. 23 Jun, 2005 1 commit
  15. 22 Jun, 2005 1 commit
  16. 21 Jun, 2005 1 commit
  17. 17 Jun, 2005 2 commits
  18. 16 Jun, 2005 2 commits
    • konstantin@mysql.com's avatar
      Fix Bug#9334 "PS API queries in log file" and · dcb0e65d
      konstantin@mysql.com authored
      Bug#8367 "low log doesn't gives complete information about prepared 
      statements"
      Implement status variables for prepared statements commands (a port of
      the patch by Andrey Hristov).
      See details in comments to the changed files.
      No test case as there is no way to test slow log/general log in 
      mysqltest.
      dcb0e65d
    • konstantin@mysql.com's avatar
      A fix for Bug#9141 "4.1 does not log into slow log · f10b3959
      konstantin@mysql.com authored
      ALTER, OPTIMIZE and ANALYZE statements".
      In 4.1 we disabled logging of slow admin statements. The fix adds an 
      option to enable it back.
      No test case (slow log is not tested in the test suite), but tested
      manually.
      + post-review fixes (word police mainly).
      f10b3959
  19. 07 Jun, 2005 1 commit
  20. 02 Jun, 2005 2 commits
  21. 01 Jun, 2005 1 commit
  22. 31 May, 2005 1 commit
    • ingo@mysql.com's avatar
      Bug#10224 - ANALYZE TABLE crashing with simultaneous CREATE ... SELECT statement. · 51d80960
      ingo@mysql.com authored
      1.) Added a new option to mysql_lock_tables() for ignoring FLUSH TABLES.
      Used the new option in create_table_from_items().
      It is necessary to prevent the SELECT table from being reopend.
      It would get new storage assigned for its fields, while the
      SELECT part of the command would still use the old (freed) storage.
      2.) Protected the CREATE TABLE and CREATE TABLE ... SELECT commands
      against a global read lock. This prevents a deadlock in
      CREATE TABLE ... SELECT in conjunction with FLUSH TABLES WITH READ LOCK
      and avoids the creation of new tables during a global read lock.
      3.) Replaced set_protect_against_global_read_lock() and
      unset_protect_against_global_read_lock() by
      wait_if_global_read_lock() and start_waiting_global_read_lock()
      in the INSERT DELAYED handling.
      51d80960
  23. 27 May, 2005 1 commit
  24. 25 May, 2005 1 commit
  25. 24 May, 2005 2 commits
  26. 28 Apr, 2005 1 commit
  27. 02 Apr, 2005 1 commit
  28. 30 Mar, 2005 1 commit
  29. 26 Mar, 2005 1 commit
  30. 24 Mar, 2005 1 commit
  31. 23 Mar, 2005 1 commit
  32. 14 Mar, 2005 1 commit
  33. 21 Feb, 2005 2 commits