An error occurred fetching the project authors.
  1. 08 Sep, 2005 1 commit
  2. 06 Sep, 2005 1 commit
  3. 15 Jul, 2005 2 commits
  4. 14 Jul, 2005 2 commits
  5. 13 Jul, 2005 4 commits
  6. 20 Jun, 2005 2 commits
  7. 07 Jun, 2005 1 commit
  8. 16 May, 2005 1 commit
  9. 05 May, 2005 1 commit
  10. 04 May, 2005 1 commit
  11. 03 May, 2005 1 commit
  12. 13 Apr, 2005 1 commit
  13. 05 Apr, 2005 1 commit
  14. 03 Mar, 2005 1 commit
    • konstantin@mysql.com's avatar
      Fixes for bug#8115 "Server Crash with prepared statement" · fe2d63a0
      konstantin@mysql.com authored
       and bug#8849 "problem with insert statement with table alias's": 
      make equality propagation work in stored procedures and prepared 
      statements.
      Equality propagation can change AND/OR structure of ON expressions,
      so the fix is to provide each execution of PS/SP with it's own
      copy of AND/OR tree. We have been doing that already for WHERE clauses,
      now ON clauses are also copied.
      fe2d63a0
  15. 02 Mar, 2005 1 commit
  16. 08 Dec, 2004 1 commit
  17. 06 Dec, 2004 1 commit
    • monty@mysql.com's avatar
      Add support for up to VARCHAR (size up to 65535) · 67ce2479
      monty@mysql.com authored
      Renamed HA_VAR_LENGTH to HA_VAR_LENGTH_PART
      Renamed in all files FIELD_TYPE_STRING and FIELD_TYPE_VAR_STRING to MYSQL_TYPE_STRING and MYSQL_TYPE_VAR_STRING to make it easy to catch all possible errors
      Added support for VARCHAR KEYS to heap
      Removed support for ISAM
      Now only long VARCHAR columns are changed to TEXT on demand (not CHAR)
      Internal temporary files can now use fixed length tables if the used VARCHAR columns are short
      67ce2479
  18. 21 Nov, 2004 1 commit
  19. 05 Nov, 2004 2 commits
  20. 27 Oct, 2004 1 commit
  21. 23 Oct, 2004 1 commit
  22. 22 Oct, 2004 4 commits
  23. 21 Oct, 2004 1 commit
  24. 13 Oct, 2004 1 commit
    • konstantin@mysql.com's avatar
      A fix and test case for Bug#5985 ""prepare stmt from "select rand(?)" · 5abc3de2
      konstantin@mysql.com authored
      crashes server." The fix makes Item_func_rand prepared-statements
      aware plus it fixes the case when RAND is used in prepared
      statements and replication is on (as well as several similar issues).
      Until now we did not reset THD before every execution of a prepared
      statement, so if some execution had set thd->time_zone_used
      or thd->rand_used they would not be reset until next mysql_parse.
      Some of post-review fixes done.
      5abc3de2
  25. 12 Oct, 2004 1 commit
  26. 09 Oct, 2004 1 commit
    • konstantin@mysql.com's avatar
      A fix and test case for Bug#5987 "subselect in bool function · daa4c249
      konstantin@mysql.com authored
      crashes server (prepared statements)": the bug was that all boolean
      items always recovered its original arguments at statement cleanup 
      stage.
      This collided with Item_subselect::select_transformer, which tries to 
      permanently change the item tree to use a transformed subselect instead of
      original one.
      So we had this call sequence for prepare:
      mysql_stmt_prepare -> JOIN::prepare -> 
      Item_subselect::fix_fields -> the item tree gets transformed ->
      Item_bool_rowready_func2::cleanup, item tree is recovered to original
      state, while it shouldn't have been;
      mysql_stmt_execute -> attempts to execute a broken tree -> crash.
      Now instead of bluntly recovering all arguments of bool functions in 
      Item_bool_rowready_func2::cleanup, we recover only those
      which were changed, and do it in one place.
      There still would exist a possibility for a collision with subselect
      tranformation, if permanent and temporary changes were performed at the 
      same stage.
      But fortunately subselect transformation is always done first, so it 
      doesn't conflict with the optimization done by propogate_cond_constants.
      Now we have: 
      mysql_stmt_prepare -> JOIN::prepare -> subselect transformation 
      permanently changes the tree -> cleanup doesn't recover anything, 
      because nothing was registered for recovery.
      mysql_stmt_execute -> JOIN::prepare (the tree is already transformed, 
      so it doesn't change), JOIN::optimize -> 
      propogate_cond_constants -> temporary changes the item tree 
      with constants -> JOIN::execute -> cleanup -> 
      the changes done by propogate_cond_constants are recovered, as
      they were registered for recovery.
      daa4c249
  27. 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
  28. 23 Sep, 2004 1 commit
  29. 17 Sep, 2004 1 commit
  30. 03 Sep, 2004 1 commit