An error occurred fetching the project authors.
- 31 Dec, 2004 1 commit
-
-
monty@mysql.com authored
This allows use to use INSERT IGNORE ... ON DUPLICATE ...
-
- 18 Dec, 2004 1 commit
-
-
monty@mysql.com authored
-
- 14 Dec, 2004 1 commit
-
-
sergefp@mysql.com authored
* Backport of safety measures from 5.0: make numeorous replaces: s/item->fix_fields()/if (!item->fixed) item->fix_fields()
-
- 13 Dec, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 11 Dec, 2004 1 commit
-
-
sergefp@mysql.com authored
Call mark_as_null_row in join_read_const and join_read_system.
-
- 30 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
now we create temporary join for all queries with subqueries to make correct cleunup of tables and avoid too early unlock (BUG#6841)
-
- 22 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
range for BETWEEN typo fixed
-
- 16 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 15 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
fixed cleunup of TMP_TABLE_PARAM (BUG#6406)
-
- 07 Nov, 2004 1 commit
-
-
monty@mysql.com authored
Now thd->mem_root is a pointer to thd->main_mem_root and THR_MALLOC is a pointer to thd->mem_root. This gives us the following benefits: - Allow us to easily detect if arena has already been swapped before (this fixes a bug in setup_conds() where arena was swaped twice in some cases) - Faster swaps of arenas (as we don't have to copy the whole MEM_ROOT) - We don't anymore have to call my_pthread_setspecific_ptr(THR_MALLOC,...) to change where memory is alloced. Now it's enough to set thd->mem_root
-
- 06 Nov, 2004 1 commit
-
-
igor@rurik.mysql.com authored
Added cases for bugs #6307 and #6460. sql_select.cc: Fixed the problem of bug reports #6307 and #6460. The reported wrong result sets were due to the fact that the added call of the fix_fields method for the built AND condition that joined WHERE and ON conditions broke ON expression, as it removed extra AND levels in the built condition. It looks like that no attributes of the built condition are needed, so we don't have to call fix_fields here.
-
- 19 Oct, 2004 1 commit
-
-
monty@mishka.local authored
Simple optimzations and cleanups Removed compiler warnings and fixed portability issues Added client functions 'mysql_embedded()' to allow client to check if we are using embedded server Fixes for purify
-
- 10 Oct, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
(Bug #4315: GROUP_CONCAT with ORDER BY returns strange results for TEXT fields Bug #5564: Strange behaviour with group_concat and distinct Bug #5970: group_concat doesn't print warnings)
-
- 09 Oct, 2004 2 commits
-
-
konstantin@mysql.com authored
change, and perform it (the new Item changes registry).
-
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.
-
- 08 Oct, 2004 2 commits
-
-
bell@sanja.is.com.ua authored
registration changing ITEM_SUM arguments added
-
konstantin@mysql.com authored
doesn't need to have it's own recovery mechanism.
-
- 07 Oct, 2004 1 commit
-
-
monty@mysql.com authored
Some bigger code changes was necessary becasue of the multi-table-update and the new HANDLER code
-
- 01 Oct, 2004 1 commit
-
-
tomas@poseidon.ndb.mysql.com authored
Fix for bug#5782: Don't choose the plan that accesses table with index_prev if the handler doesn't support it (see also ChangeSet@1.2039)
-
- 30 Sep, 2004 2 commits
-
-
tomas@poseidon.ndb.mysql.com authored
-
dlenev@brandersnatch.localdomain authored
identical to another in result" According to SQL standard queries like "select t1.a as col from t1, t2 order by a" should return an error if both tables contain field a.
-
- 13 Sep, 2004 2 commits
-
-
joreland@mysql.com authored
-
serg@serg.mylan authored
-
- 06 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
fixed temporary table processing expresions of subqueries and removed wrong restrictions of field resolving (BUG#5326)
-
- 03 Sep, 2004 1 commit
-
-
igor@rurik.mysql.com authored
Added a test case for bug #5333. null_key.result, key_primary.result: Made covering index usable for const tables. sql_select.cc: Made covering index usable for const tables: downported the corresponding code from 4.1. Simultaneously fixed bug #5333 reported for 4.1. The bug was due to the fact that field index in join structures was always set to 0 for const tables.
-
- 31 Aug, 2004 2 commits
-
-
bell@sanja.is.com.ua authored
-
monty@mysql.com authored
Use 'mysqltest' as test database instead of test_$1 or test1,test2 to not accidently delete an important database Safety fix for mailformed MERGE files
-
- 29 Aug, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 26 Aug, 2004 1 commit
-
-
monty@mysql.com authored
Fixed bug in end space handle for WHERE text_column="constant"
-
- 24 Aug, 2004 2 commits
-
-
konstantin@mysql.com authored
execute crashes server": we were deleting lex->result after each execute, but prepared statements assumed that it's left intact. The fix adds cleanup() method to select_result hierarchy, so that result objects can be reused. Plus we now need to delete result objects more wisely.
-
monty@mysql.com authored
-
- 23 Aug, 2004 5 commits
-
-
gluh@gluh.mysql.r18.ru authored
-
gluh@gluh.mysql.r18.ru authored
wrong results
-
monty@mysql.com authored
Cosmetic cleanups Don't call 'delete_elements' on copy_funcs as this causes elements to be freed twice
-
serg@serg.mylan authored
-
sergefp@mysql.com authored
* When executing EXPLAIN, do the same as for the query: convert join type to JT_CONST if keyuse array covers all key parts and all of them are constants. * In remove_const, don't remove conditions that depend on some-const-table and current-table.
-
- 20 Aug, 2004 3 commits
-
-
konstantin@mysql.com authored
a second time". The bug was caused by incompatibility of negations elimination algorithm and PS: during first statement execute a subtree with negation was replaced with equivalent subtree without NOTs. The problem was that although this transformation was permanent, items of the new subtree were created in execute-local memory. The patch adds means to check if it is the first execute of a prepared statement, and if this is the case, to allocate items in memory of the prepared statement. The implementation: - backports Item_arena from 5.0 - adds Item_arena::is_stmt_prepare(), Item_arena::is_first_stmt_execute(). - deletes THD::allocate_temporary_pool_for_ps_preparing(), THD::free_temporary_pool_for_ps_preparing(); they were redundant. and adds a few invariants: - thd->free_list never contains junk (= freed items) - thd->current_arena is never null. If there is no prepared statement, it points at the thd. The rest of the patch contains mainly mechanical changes and cleanups.
-
serg@serg.mylan authored
-
dlenev@brandersnatch.localdomain authored
When in find_item_in_list() we are looking for item we should take into account unaliased names of the fields but only if item with such aliased name is not found. Also we should ignore aliases when looking for fully specified field.
-
- 19 Aug, 2004 1 commit
-
-
serg@serg.mylan authored
-