An error occurred fetching the project authors.
- 08 Sep, 2005 1 commit
-
-
andrey@lmy004. authored
are thus dangling later)
-
- 06 Sep, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
Argument of RAND function can be constant value only
-
- 15 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
of system vars at PREPARE time": implement a special Item to handle system variables. This item substitutes itself with a basic constant containing variable value at fix_fields.
-
tomas@poseidon.ndb.mysql.com authored
-
- 14 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
syntax in binlog which stops replication": disallow the use of parameter markers which can lead to generation of malformed binlog queries.
-
- 13 Jul, 2005 4 commits
-
-
konstantin@mysql.com authored
character set is UCS2". The bug is no longer repeatable.
-
konstantin@mysql.com authored
binary).
-
konstantin@mysql.com authored
-
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.
-
- 20 Jun, 2005 2 commits
-
-
dlenev@brandersnatch.localdomain authored
INSERT ... SELECT with UNION" (reviewed version). Altough bug manifest itself only starting from 5.0 it is better to apply fix to 4.1 to keep some assumptions true and make code more future-proof.
-
msvensson@neptunus.(none) authored
- Print warning that says display width is not supported for datatype TIMESTAMP, if user tries to create a TIMESTAMP column with display width. - Use display width for TIMESTAMP only in type_timestamp test to make sure warning is displayed correctly.
-
- 07 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
error for LIMIT placeholder". The patch adds grammar support for LIMIT ?, ? and changes the type of ST_SELECT_LEX::select_limit,offset_limit from ha_rows to Item*, so that it can point to Item_param.
-
- 16 May, 2005 1 commit
-
-
monty@mysql.com authored
Fixed bug in mysql_stmt_fetch() when retrieving rows to return
-
- 05 May, 2005 1 commit
-
-
konstantin@mysql.com authored
should return a non empty one" (see comments for the changed files for details).
-
- 04 May, 2005 1 commit
-
-
konstantin@mysql.com authored
records if prepared statements is used" (see comments to the changed files).
-
- 03 May, 2005 1 commit
-
-
konstantin@mysql.com authored
records if prepared statements is used". This fix changes equality evaluation method of basic constants from by-name to by-value, thus effectively enabling use of parameter markers in some optimizations (constants propagation, evaluation of possible keys for query).
-
- 13 Apr, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 05 Apr, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
restore original 'lex->query_tables' table list after processing of information schema table remove unnecessary operations
-
- 03 Mar, 2005 1 commit
-
-
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.
-
- 02 Mar, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 08 Dec, 2004 1 commit
-
-
konstantin@mysql.com authored
during execute"
-
- 06 Dec, 2004 1 commit
-
-
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
-
- 21 Nov, 2004 1 commit
-
-
konstantin@mysql.com authored
of <parameter> IS NULL": we must not only set Item::null_value in Item_param, but implement Item_param::is_null() to work well with IS NULL/IS NOT NULL clauses.
-
- 05 Nov, 2004 2 commits
-
-
konstantin@mysql.com authored
and blank after function name". Crop fruits of copy-paste programming: pre-caching of stored functions wasn't performed for prepared statements just because implementation of prepared statements is done as an add-on to the main execution flow, and the preload was originally implemented for main execution branch only (mysql_execute_command).
-
bar@mysql.com authored
Bug #6351 make test failure "Unknown character set" UCS2 related tests were moved into ctype_ucs.
-
- 27 Oct, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 23 Oct, 2004 1 commit
-
-
monty@mysql.com authored
Fixed wrong range test code for HEAP tables. This caused a crash when doing a range test with a key that didn't have lower or upper bound (Bug #6082) More test cases
-
- 22 Oct, 2004 4 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
prepared statements when LIMIT is used" and post-review comments. The fix changes the approach we calculate the need for ORDER BY in UNION: the previous was not PS friendly, as it damaged SELECT_LEX options in case of single select.
-
monty@mysql.com authored
Fixed checking of privilege handling in CREATE ... SELECT (Bug #6094)
-
konstantin@mysql.com authored
names with ident. tables fr. diff. schemata": revise all uses of Item_field and make them prepared-statements friendly when necessary.
-
- 21 Oct, 2004 1 commit
-
-
igor@rurik.mysql.com authored
Post-merge fixes. sql_select.cc: Post-merge cleanup.
-
- 13 Oct, 2004 1 commit
-
-
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.
-
- 12 Oct, 2004 1 commit
-
-
konstantin@mysql.com authored
propogation works only once (prepared statements)".
-
- 09 Oct, 2004 1 commit
-
-
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.
-
- 07 Oct, 2004 1 commit
-
-
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.
-
- 23 Sep, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 17 Sep, 2004 1 commit
-
-
konstantin@mysql.com authored
key Column Fails".
-
- 03 Sep, 2004 1 commit
-
-
konstantin@mysql.com authored
server': the bug occurs when arguments of LIKE function are in differentcharacter sets. If these character sets are compatible, we create an item-converter. In prepared mode, this item needs to be created in memory of current prepared statement.
-