An error occurred fetching the project authors.
  1. 27 Jun, 2006 1 commit
  2. 19 Jun, 2006 1 commit
    • holyfoot@deer.(none)'s avatar
      bug #20318 (ctype_ucs2_def test fails with embedded) · d8d42948
      holyfoot@deer.(none) authored
      there was two problems about charsets in embedded server
      1. mysys/charset.c - defined there default_charset_info variable is
      modified by both server and client code (particularly when
      --default-charset option is handled)
      In embedded server we get two codelines modifying one variable.
      I created separate default_client_charset_info for client code
      
      2. mysql->charset and mysql->options.charset initialization isn't
      properly done for embedded server - necessary calls added
      d8d42948
  3. 01 Jun, 2006 1 commit
    • holyfoot@deer.(none)'s avatar
      bug #16017 (memory leaks in embedded server) · bc35c500
      holyfoot@deer.(none) authored
      There actually was 3 different problems -
      hash_user_connections wasn't cleaned
      one strdupped database name wasn't freed
      and stmt->mem_root wasn't cleaned as it was
      replased with mysql->field_alloc for result
      For the last one - i made the library using stmt's
      fields to store result if it's the case.
      bc35c500
  4. 28 May, 2006 1 commit
    • evgen@moonbone.local's avatar
      Fixed bug#19225: unchecked error results in server crash · 1f30bf5a
      evgen@moonbone.local authored
      In multi-table delete a table for delete can't be used for selecting in
      subselects. Appropriate error was raised but wasn't checked which leads to a
      crash at the execution phase.
      
      The mysql_execute_command() now checks for errors before executing select
      for multi-delete.
      1f30bf5a
  5. 26 Apr, 2006 1 commit
  6. 25 Apr, 2006 2 commits
  7. 21 Apr, 2006 1 commit
    • igor@rurik.mysql.com's avatar
      Fixed bug #18767. · fc751415
      igor@rurik.mysql.com authored
      The bug caused wrong result sets for union constructs of the form
      (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2.
      For such queries order lists were concatenated and limit clause was
      completely neglected. 
      fc751415
  8. 21 Feb, 2006 1 commit
  9. 26 Jan, 2006 1 commit
  10. 07 Dec, 2005 1 commit
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · 5aa315e2
      ingo@mysql.com authored
      Problem #1: INSERT...SELECT, Version for 4.1.
      INSERT ... SELECT with the same table on both sides (hidden
      below a MERGE table) does now work by buffering the select result.
      The duplicate detection works now after open_and_lock_tables() 
      on the locks.
      I did not find a test case that failed without the change in
      sql_update.cc. I made the change anyway as it should in theory
      fix a possible MERGE table problem with multi-table update.
      5aa315e2
  11. 04 Dec, 2005 1 commit
  12. 29 Nov, 2005 1 commit
    • ingo@mysql.com's avatar
      BUG#5390 - problems with merge tables · 76861ac6
      ingo@mysql.com authored
      Problem #1: INSERT...SELECT
      INSERT ... SELECT with the same table on both sides (hidden
      below a MERGE table) does now work by buffering the select result.
      The duplicate detection works now after open_and_lock_tables() 
      on the locks.
      I did not find a test case that failed without the change in
      sql_update.cc. I made the change anyway as it should in theory
      fix a possible MERGE table problem with multi-table update.
      76861ac6
  13. 10 Oct, 2005 2 commits
  14. 08 Oct, 2005 1 commit
  15. 19 Sep, 2005 1 commit
  16. 14 Sep, 2005 1 commit
  17. 10 Sep, 2005 1 commit
  18. 05 Sep, 2005 1 commit
  19. 03 Sep, 2005 1 commit
  20. 01 Sep, 2005 2 commits
  21. 31 Aug, 2005 2 commits
    • lars@mysql.com's avatar
      BUG#12542: All set statements should be executed by slave thd · 7fd89c85
      lars@mysql.com authored
      rpl_replicate_do.result:
        New test case
      sql_parse.cc:
        All SET statements should be executed by slave thd
      rpl_replicate_do.test:
        New test case
      7fd89c85
    • bar@mysql.com's avatar
      · f2ea1ac8
      bar@mysql.com authored
        bug#9948 changed client-charset behavior in 4.1.x libmysql, which issue BC prob
      
      sql_parse.cc:
      mysqld.cc:
      
        Added --skip-client-character-set-handshake.
        When this option is activated, client side character set
        (which is sent in handshake) is ignored, and server side
        default-character-set value is used for character_set_client
        and character_set_results, thus reprodicing 4.0 behaviour.
      f2ea1ac8
  22. 29 Aug, 2005 1 commit
  23. 15 Aug, 2005 1 commit
  24. 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
  25. 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
  26. 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
  27. 05 Aug, 2005 1 commit
  28. 25 Jul, 2005 1 commit
  29. 23 Jul, 2005 1 commit
  30. 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
  31. 28 Jun, 2005 2 commits
  32. 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
  33. 23 Jun, 2005 1 commit
  34. 22 Jun, 2005 1 commit