An error occurred fetching the project authors.
- 15 Sep, 2005 1 commit
-
-
evgen@moonbone.local authored
Optimizer did choose "Range checked for each record" for one of the tables. For first few loops over that table it choose sequential access, on later stage it choose to use index. Because table was previously initialized for sequential access, it skips intitialization for index access, and when server tries to retrieve data error occurs. QUICK_RANGE_SELECT::init() changes so if file already initialized for sequential access, it calls ha_rnd_end() and initializes file for index access.
-
- 07 Sep, 2005 1 commit
-
-
aivanov@mysql.com authored
Post merge changes sql_yacc.yy: Post merge changes sql_select.cc: Fixed bugs #12101, #12102: wrong calculation of not_null_tables() for some expressions (post merge changes). The function add_key_fields() is modified. There cannot be NOT before BETWEEN/IN anymore. Rather Item_func_between/in objects can represent now [NOT]BETWEEN/IN expressions.
-
- 06 Sep, 2005 1 commit
-
-
aivanov@mysql.com authored
Fixed bugs #12101, #12102: wrong calculation of not_null_tables() for some expressions. The classes Item_func_between, Item_func_if, Item_func_in are modified. Item_func_between/in objects can represent now [NOT]BETWEEN/IN expressions. The class Item_func_opt_neg is added to factor out the functionality common for the modified classes Item_func_between and Item_func_in. item_cmpfunc.cc: Fixed bugs #12101, #12102: wrong calculation of not_null_tables() for some expressions. Added Item_func_between::fix_fields(), Item_func_if::fix_fields(), Item_func_in::fix_fields(). They correct generic calculation of the not_null_tables attribute when it is needed. Modified Item_func_between::val_int(), Item_func_in::val_int(). opt_range.cc: Fixed bugs #12101, #12102: wrong calculation of not_null_tables() for some expressions. The function get_mm_tree() is modified. There cannot be NOT before BETWEEN/IN anymore. Rather Item_func_between/in objects can represent now [NOT]BETWEEN/IN expressions. sql_yacc.yy: Fixed bugs #12101, #12102: wrong calculation of not_null_tables() for some expressions. Item_func_between/in objects can represent now [NOT]BETWEEN/IN expresions. join_outer.result: Fixed some testcases results (bugs #12101, #12102) join_outer.test: Added testcases for bugs #12101, #12102
-
- 29 Aug, 2005 2 commits
-
-
sergefp@mysql.com authored
doesn't continue reading the last range.
-
timour@mysql.com authored
-
- 18 Jul, 2005 1 commit
-
-
monty@mishka.local authored
Changed defaults option --instance to --defaults-group-suffix Changed option handling to allow --defaults-file, --defaults-extra-file and --defaults-group-suffix to be given in any order Changed MYSQL_INSTANCE to MYSQL_GROUP_SUFFIX mysql_print_defaults now understands --defaults-group-suffix Remove usage of my_tempnam() (not safe function) if( -> if ( and while( to while (
-
- 16 Jul, 2005 1 commit
-
-
igor@rurik.mysql.com authored
Fixed bug #11853. Corrected the code of the range optimization for NOT IN and NOT BETWEEN. range.test, range.result: Fixed bug #11853.
-
- 04 Jul, 2005 1 commit
-
-
monty@mysql.com authored
- Mostly indentation fixes - Added missing test - Ensure that Item_func_case() checks for stack overruns - Use real_item() instead of (Item_ref*) item - Fixed wrong error handling
-
- 29 Jun, 2005 1 commit
-
-
monty@mysql.com authored
nsure that delete works not only on table->record[0] for federated tables
-
- 28 Jun, 2005 6 commits
-
-
igor@rurik.mysql.com authored
Fixed a compilation error.
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY select within select". The bug was caused by the reset of thd->mem_root to thd->main_mem_root in Item_subselect::exec, which in turn triggered too early free_root() for data which was needed on subsequent fetches from a cursor. This reset also caused a memory leak in stored procedures, as subsequent executions of instructions containing a subselect were allocating memory in thd->main_mem_root, which is not freed until the end of the entire SP, instead of the per-call mem_root, which is freed in the end of execution of the instruction.
-
igor@rurik.mysql.com authored
Added a test case for bug #10031. opt_range.cc: Fixed bug #10031: range condition was not used with views. Range analyzer did not take into account that view columns were always referred through Item_ref.
-
monty@mysql.com authored
This fixed a failure of insert_update.test on some platforms
-
kent@mysql.com authored
Added missing `;' to DBUG_RETURN()
-
- 23 Jun, 2005 3 commits
-
-
igor@rurik.mysql.com authored
Identation correction.
-
igor@rurik.mysql.com authored
Fixed buf #11487. Added a call of QUICK_RANGE_SELECT::init to the QUICK_RANGE_SELECT::reset method. Without it the second evaluation of a subquery employing the range access failed. subselect.result, subselect.test: Added a test case for bug #11487.
-
timour@mysql.com authored
The source of the problem is in Field_longlong::cmp. If 'this' is an unsigned number, the method casts both the current value, and the constant that we compare with to an unsigned number. As a result if the constant we compare with is a negative number, it wraps to some unsigned number, and the comparison is incorrect. When the optimizer chooses the "range" access method, this problem causes handler::read_range_next to reject the current key when the upper bound key is a negative number because handler::compare_key incorrectly considers the positive and negative keys to be equal. The current patch does not correct the source of the problem in Field_longlong::cmp because it is not easy to propagate sign information about the constant at query execution time. Instead the patch changes the range optimizer so that it never compares unsiged fields with negative constants. As an added benefit, queries that do such comparisons will execute faster because the range optimizer replaces conditions like: (a) (unsigned_int [< | <=] negative_constant) == FALSE (b) (unsigned_int [> | >=] negative_constant) == TRUE with the corresponding constants. In some cases this may even result in constant time execution.
-
- 22 Jun, 2005 1 commit
-
-
svoj@mysql.com authored
Fix GCC 4.0 link failure. Better CXX_VERSION guessing.
-
- 20 Jun, 2005 1 commit
-
-
sergefp@mysql.com authored
KEY_PART_INFO::store_length, not KEY_PART_INFO::length (like range code does)
-
- 19 Jun, 2005 1 commit
-
-
svoj@mysql.com authored
Fix for yaSSL link failures with Forte Developer 7, MIPSpro Compilers, Compaq C++. These compilers have problem with implicit template instantiation in archives (libyassl.a, libtaocrypt.a). Instantiate templates explicitly. Fix for yaSSL link failure on powermacg5 (gcc 3.3). When -O3 is specified gcc inlines __cxa_pure_virtual. This is wrong behavior, __cxa_pure_virtual must never be inlined.
-
- 14 Jun, 2005 1 commit
-
-
timour@mysql.com authored
The problem was that when there was no MIN or MAX function, after finding the group prefix based on the DISTINCT or GROUP BY attributes we did not search further for a key in the group that satisfies the equi-join conditions on attributes that follow the group attributes. Thus we ended up with the wrong rows, and subsequent calls to select_cond->val_int() in evaluate_join_record() were filtering those rows. Hence - the query result set was empty. The problem occured both for GROUP BY queries without MIN/MAX and for queries with DISTINCT (which were internally executed as GROUP BY queries).
-
- 05 Jun, 2005 1 commit
-
-
serg@serg.mylan authored
'#pragma interface' (that comes with the #include'd header file)
-
- 03 Jun, 2005 1 commit
-
-
monty@mysql.com authored
Ensure that 'null_value' is not accessed before val() is called in FIELD() functions Fixed initialization of key maps. This fixes some problems with keys when you have more than 64 keys Fixed that ROLLUP don't always create a temporary table. This fix ensures that func_gconcat.test results are now predictable
-
- 02 Jun, 2005 1 commit
-
-
kent@mysql.com authored
Set #pragma implementation" earlier Many files: Need to include <my_global.h> before #ifdef USE_PRAGMA_IMPLEMENTATION
-
- 01 Jun, 2005 1 commit
-
-
monty@mysql.com authored
Ensure we get error if INSERT IGNORE ... SELECT fails Fixed wrong key_part->key_length usage in index_merge
-
- 30 May, 2005 2 commits
-
-
monty@mysql.com authored
-
konstantin@mysql.com authored
"the server side preparedStatement error for LIMIT placeholder", which moves all uses of LIMIT clause from PREPARE to OPTIMIZE and later steps. After-review fixes.
-
- 26 May, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
Added some more ifdefs for "#pragma interface"
-
- 25 May, 2005 1 commit
-
-
monty@mysql.com authored
Added ASSERT() to detect wrongly packed fields
-
- 21 May, 2005 2 commits
-
-
igor@rurik.mysql.com authored
Post review corrections for optimization request #10561.
-
igor@rurik.mysql.com authored
Added test cases for optimization request #10561. opt_range.cc, sql_select.cc: Fixed bug #10561: an optimization request to allow range analysis for NOT IN and NOT BETWEEN.
-
- 19 May, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
Cset exclude: msvensson@neptunus.(none)|ChangeSet|20050425090838|60886
-
- 09 May, 2005 1 commit
-
-
ramil@ram-book.(none) authored
-
- 06 May, 2005 1 commit
-
-
monty@mishka.local authored
Added option --count to mysqlshow (to show number of rows) Fixed possible core dump in information schema
-
- 28 Apr, 2005 1 commit
-
-
sergefp@mysql.com authored
Make get_quick_select_for_ref() accept estimated # records as parameter and set QUICK_RANGE_SELECT::records, as this value is used to allocate buffers in Multi-Range Read.
-
- 25 Apr, 2005 2 commits
-
-
sergefp@mysql.com authored
BUG#10037: A proper fix: Add 0.01 to cost of 'range' scans, don't add 0.01 to cost of the 'index' scan.
-
msvensson@neptunus.(none) authored
-
- 20 Apr, 2005 1 commit
-
-
sergefp@mysql.com authored
* Add 0.01 to cost of 'range'+'using index' scan to avoid optimizer choice races with 'index' scan.
-
- 18 Apr, 2005 1 commit
-
-
sergefp@mysql.com authored
Don't produce data truncation warnings from within cp_buffer_from_ref(). This function is only used to make index search tuples and data truncation that occurs here has no relation with truncated values being saved into tables.
-