An error occurred fetching the project authors.
- 24 Oct, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
ucs2 doesn't provide required by fulltext ctype array. Crash happens because fulltext attempts to use unitialized ctype array. Fixed by converting ucs2 fields to compatible utf8 analogue.
-
- 13 Jun, 2007 1 commit
-
-
joerg@trift2. authored
Improved check for thread identity in the "embedded" case, provided by Monty. This finishes the fixes for bug#27078.
-
- 03 May, 2007 1 commit
-
-
evgen@moonbone.local authored
The generic string to int conversion was used by the Item_func_signed and the Item_func_unsigned classes to convert DATE/DATETIME values to the SIGNED/UNSIGNED type. But this conversion produces wrong results for such values. Now if the item which result has to be converted can return its result as longlong then the item->val_int() method is used to allow the item to carry out the conversion itself and return the correct result. This condition is checked in the Item_func_signed::val_int() and the Item_func_unsigned::val_int() functions.
-
- 12 Apr, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
IGNORE/USE/FORCE INDEX hints were honored when choosing FULLTEXT index. With this fix these hints are ignored. For regular indexes we may perform table scan instead of index lookup when IGNORE INDEX was specified. We cannot do this for FULLTEXT in NLQ mode.
-
- 26 Jan, 2007 1 commit
-
-
igor@olga.mysql.com authored
The bug report has demonstrated the following two problems. 1. If an ORDER/GROUP BY list includes a constant expression being optimized away and, at the same time, containing single-row subselects that return more that one row, no error is reported. Strictly speaking the standard allows to ignore error in this case. Yet, now a corresponding fatal error is reported in this case. 2. If a query requires sorting by expressions containing single-row subselects that, however, return more than one row, then the execution of the query may cause a server crash. To fix this some code has been added that blocks execution of a subselect item in case of a fatal error in the method Item_subselect::exec.
-
- 22 Jan, 2007 1 commit
-
-
igor@olga.mysql.com authored
The bug is actually a duplicate of the bug 14708. Down-ported the fix for 14708 from 5.0. Merged the test case for bug 14708 from 5.0.
-
- 09 Jan, 2007 1 commit
-
-
kroki/tomash@moonlight.home authored
server The problem was that when memory was exhausted HEAP engine could crash (GROUP BY uses HEAP TABLE). Alternatively, if SET was used, it could report an error "You may only use constant expressions with SET" instead of "Out of memory (Needed NNNNNN bytes)". The solution is: - pass MY_WME to (some) calls to my_malloc() to get correct message. - fix heap_write() so that the first key is skipped during cleanup on ENOMEM because it wasn't inserted and doesn't have to be deleted. No test case is provided because we can't test out-of-memory behaviour in our current test framework.
-
- 13 Nov, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
-
- 06 Nov, 2006 1 commit
-
-
cmiller@zippy.cornsilk.net authored
The Item_func_mod objects never had maybe_null set, so users had no reason to expect that they can be NULL, and may therefore deduce wrong results. Now, set maybe_null.
-
- 06 Oct, 2006 1 commit
-
-
kroki/tomash@moonlight.intranet authored
Note: bug#21726 does not directly apply to 4.1, as it doesn't have stored procedures. However, 4.1 had some bugs that were fixed in 5.0 by the patch for bug#21726, and this patch is a backport of those fixes. Namely, in 4.1 it fixes: - LAST_INSERT_ID(expr) didn't return value of expr (4.1 specific). - LAST_INSERT_ID() could return the value generated by current statement if the call happens after the generation, like in CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT); INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID()); - Redundant binary log LAST_INSERT_ID_EVENTs could be generated.
-
- 13 Sep, 2006 1 commit
-
-
kaa@polly.local authored
Cset exclude: kaa@polly.local|ChangeSet|20060908100829|09983
-
- 12 Sep, 2006 1 commit
-
-
kaa@polly.local authored
-
- 08 Sep, 2006 1 commit
-
-
kaa@polly.local authored
- Honor unsigned_flag in the corresponding functions - Use compare_int_signed_unsigned()/compare_int_unsigned_signed() instead of explicit comparison in GREATEST() and LEAST()
-
- 14 Jun, 2006 1 commit
-
-
bar@mysql.com authored
Problem: cast to unsigned limited result to max signed bigint 9223372036854775808, instead of max unsigned bigint 18446744073709551615. Fix: don't use args[0]->val_int() when casting from a floating point number, use val() instead, with range checkings, special to unsigned data type. item_func.cc: Special handling of cast from REAL_RESULT to unsigned int: we cannot execute args[0]->val_int() because it cuts max allowed value to LONGLONG_INT, instead of ULONGLONG_INT required. count_distinct3.test: Getting rid of "Data truncated; out of range ..." warnings. cast.test, cast.result: Adding test case. ps.result: Fixing that cast from 6570515219.6535 to unsigned didn't round to 6570515220, and returned 6570515219 instead.
-
- 07 Jun, 2006 1 commit
-
-
ramil@mysql.com authored
-
- 05 May, 2006 1 commit
-
-
aelkin@mysql.com authored
The reason of the bug is in that `get_var_with_binlog' performs missed assingment of the variables as side-effect. Doing that it eventually calls `free_underlaid_joins' to pass as an argument `thd->lex->select_lex' of the lex which belongs to the user query, not to one which is emulated i.e SET @var1:=NULL. `get_var_with_binlog' is refined to supply a temporary lex to sql_set_variables's stack.
-
- 24 Apr, 2006 1 commit
-
-
kroki@mysql.com authored
Update User_level_lock::thread_id on acquiring an existing lock, and reset it on lock release.
-
- 12 Apr, 2006 1 commit
-
-
evgen@moonbone.local authored
used In a simple queries a result of the GROUP_CONCAT() function was always of varchar type. But if length of GROUP_CONCAT() result is greater than 512 chars and temporary table is used during select then the result is converted to blob, due to policy to not to store fields longer than 512 chars in tmp table as varchar fields. In order to provide consistent behaviour, result of GROUP_CONCAT() now will always be converted to blob if it is longer than 512 chars. Item_func_group_concat::field_type() is modified accordingly.
-
- 07 Nov, 2005 1 commit
-
-
sasha@asksasha.com authored
transaction while holding the lock. Also test to make sure other binlogging issues reported in the bug have been addressed.
-
- 06 Nov, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 01 Nov, 2005 1 commit
-
-
monty@mysql.com authored
Removed wrong fix for bug #14009 (use of abs() on null value causes problems with filesort) Mark that add_time(), time_diff() and str_to_date() can return null values
-
- 18 Oct, 2005 2 commits
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
jimw@mysql.com authored
-
- 15 Oct, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 07 Oct, 2005 1 commit
-
-
bar@mysql.com authored
Adding test case. item_func.cc: Bug#13751 find_in_set: Illegal mix of collations. Character set conversion was forgotten in find_in_set.
-
- 06 Sep, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
Argument of RAND function can be constant value only
-
- 26 Jul, 2005 1 commit
-
-
bar@mysql.com authored
Adding test item_sum.cc: Adding a call for collation/charset aggregation, to collect attributes from the arguments. The actual bug fix. item_func.h, item_func.cc, item.h, item.cc: - Removing collation aggrgation functions from Item_func class in item.cc, and adding it as non-class functions in item.cc to be able to reuse this code for group_concat. - Adding replacement for these functions into Item_func class as wrappers for moved functions, to minizize patch size,
-
- 25 Jul, 2005 1 commit
-
-
jimw@mysql.com authored
was used. (Bug #10724)
-
- 19 Jul, 2005 1 commit
-
-
monty@mishka.local authored
-
- 15 Jul, 2005 1 commit
-
-
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.
-
- 14 Jul, 2005 1 commit
-
-
sergefp@mysql.com authored
source table present (this happens for ORDER BY after UNION)
-
- 13 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
binary).
-
- 23 Jun, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 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 2 commits
-
-
bar@mysql.com authored
set_var.cc: variables.result variables.test Bug #10904 Illegal mix of collations between a system variable and a constant Changing coercibility of system variables to SYSCONST, to be the same with USER(), DATABASE(), etc.
-
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
-
-
jimw@mysql.com authored
-
- 26 May, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
Added some more ifdefs for "#pragma interface"
-
- 14 May, 2005 1 commit
-
-
monty@mysql.com authored
-