An error occurred fetching the project authors.
  1. 08 Oct, 2004 2 commits
  2. 07 Oct, 2004 1 commit
    • konstantin@mysql.com's avatar
      A fix for Bug#5748 "Prepared statement with BETWEEN and bigint values · 2aa7ec0d
      konstantin@mysql.com authored
      crashes mysqld": implementation for a generic item tree modifications
      registry. Every item tree modification which should be rolled back for
      subsequent execution of a prepared statement or stored procedure should
      be saved in the registry. All such modifications are rolled back at once
      during cleanup stage of PS.
      Actual fix for the bug just adds a call to register modifications to
      convert_constant_item.
      Post review fixes implemented.
      2aa7ec0d
  3. 25 Sep, 2004 1 commit
  4. 16 Sep, 2004 1 commit
  5. 01 Sep, 2004 1 commit
  6. 31 Aug, 2004 1 commit
  7. 11 Aug, 2004 1 commit
  8. 28 Jun, 2004 1 commit
  9. 26 Jun, 2004 1 commit
  10. 25 Jun, 2004 1 commit
  11. 18 Jun, 2004 1 commit
  12. 17 Jun, 2004 1 commit
  13. 16 Jun, 2004 2 commits
  14. 08 Jun, 2004 1 commit
  15. 07 Jun, 2004 1 commit
  16. 31 May, 2004 1 commit
  17. 24 May, 2004 1 commit
  18. 21 May, 2004 1 commit
  19. 06 May, 2004 1 commit
    • monty@mysql.com's avatar
      Portability fixes · 939ea71e
      monty@mysql.com authored
      Change strtoll -> my_strtoll10()
      Fixed bug in my_strntoul() and my_strntol() where we got different values on 32 and 64 bit systems (Bug #3472)
      939ea71e
  20. 05 May, 2004 1 commit
  21. 04 May, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      Fix for remaining issues described in Bug #1664 · c7fbcbca
      dlenev@brandersnatch.localdomain authored
      "mysql_send_long_data() API call is completely broken".
      
      Now we are resetting some members (long_data_supplied/null_value...) of Item_param to its 
      initial state after each execution of prepared statement. We also manipulating 
      Item_param::maybe_null/null_value only via Item_param::set_* setters which makes code a bit 
      more robust.
      c7fbcbca
  22. 28 Apr, 2004 1 commit
  23. 11 Apr, 2004 1 commit
  24. 05 Apr, 2004 1 commit
    • sergefp@mysql.com's avatar
      Many files: · a8386d01
      sergefp@mysql.com authored
        SQL Syntax for Prepared Statements (WL#1622)
      ps.test, ps.result:
        new file
      a8386d01
  25. 31 Mar, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      Fix for Bug #3307 "FLUSH TABLES sometimes breaks prepared statement · 4122188c
      dlenev@brandersnatch.localdomain authored
      table resolution".
      Added members to Item_ident for storing original db, table and field
      names since those that set later from Field have shorter life-time 
      than required by prep. stmt. So we need to restore original names in 
      Item_ident::cleanup(). Also now using special construnctor for creation
      of Item_field from Field object that ensures that table and field name 
      have big enough life-time.
      
      "Fix" for bug #2050 "10 to 1 performance drop with server 4.1.1"
      Clean ups in implementation of caching of field number in table.
      Added caching of table in which field is found in find_field_in_tables(). 
      4122188c
  26. 28 Mar, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      "Fix" for BUG #2050 "10 to 1 performance drop with server 4.1.1". · 9e28b769
      dlenev@brandersnatch.localdomain authored
      Actually it is not a bug but right behavior observed as pefomance 
      degradation after we have forced Item_field::fix_fields() to 
      re-execute each time when we are executing prep stmt.
      
      This patch implements small optimization which heals this bad 
      behavior. We are caching field position in TABLE::field array in
      Item's member and are using this position for speeding up field
      lookups in fix_fields() in case of its re-execution.
      9e28b769
  27. 25 Mar, 2004 1 commit
  28. 20 Mar, 2004 1 commit
  29. 18 Mar, 2004 2 commits
  30. 17 Mar, 2004 2 commits
  31. 16 Mar, 2004 1 commit
  32. 15 Mar, 2004 1 commit
    • konstantin@mysql.com's avatar
      Fixes for bugs #2274 "mysqld gets SIGSEGV during processing of malformed · e43ac760
      konstantin@mysql.com authored
      COM_EXECUTE packet" and #2795 "prepare + execute without bind_param crashes
       server" and #2473 "seg fault running tests/client_test.c": 
      - length checking added to packet parser 
      - default impelemntation of Item_param::set_param_func will work in
      case of malformed packet.
      No test cases are possible in our test suite, as there are no tests 
      operating on protocol layer.
      e43ac760
  33. 03 Mar, 2004 1 commit
  34. 02 Mar, 2004 1 commit
  35. 27 Feb, 2004 2 commits