An error occurred fetching the project authors.
- 09 Dec, 2008 1 commit
-
-
Sergey Glukhov authored
the problem: FORMAT func max_length value was calculated incorrectly the fix: correct calculation of max_length
-
- 30 Oct, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
Item_func_inet_ntoa and Item_func_conv inherit 'maybe_null' flag from an argument, which is wrong. Both can be NULL with notnull arguments, so that's fixed.
-
- 21 Oct, 2007 1 commit
-
-
kaa@polly.(none) authored
Since, as of MySQL 5.0.15, CHAR() arguments larger than 255 are converted into multiple result bytes, a single CHAR() argument can now take up to 4 bytes. This patch fixes Item_func_char::fix_length_and_dec() to take this into account. This patch also fixes a regression introduced by the patch for bug21513. As now we do not always have the 'name' member of Item set for Item_hex_string and Item_bin_string, an own print() method has been added to Item_hex_string so that it could correctly be printed by Item_func::print_args().
-
- 19 Oct, 2007 1 commit
-
-
Problem: lying to the optimizer that a function (Item_func_inet_ntoa) cannot return NULL values leads to unexpected results (in the case group keys creation/comparison is broken). Fix: Item_func_inet_ntoa::maybe_null should be set properly.
-
- 11 Oct, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
Bug#30982 CHAR(..USING..) can return a not-well-formed string Bug#30986 Character set introducer followed by a HEX string can return bad result check_well_formed_result moved to Item from Item_str_func fixed Item_func_char::val_str for proper ucs symbols converting added check for well formed strings for correct conversion of constants with underscore charset
-
- 27 Jul, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
Item_func_user doesn't calculate anything in it's val_str() method, just returns saved str_value. Though Item::save_in_field method can destroy str_value, relying on val_str() return. As a result we get the garbage stored in field. We cannot use Item::save_in_field implementation for Item_func_user, reimplement it in simpler way.
-
- 11 Apr, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
The function CRC32() returns unsigned integer. But the metadata (the unsigned flag) for the function was set incorrectly. As a result type arithmetics based on the function's metadata (like finding the concise type of an temporary table column to hold the result) returned incorrect results. Fixed by returning correct type information. This fix is based on code contributed by Martin Friebe (martin@hybyte.com) on 2007-03-30.
-
- 02 Mar, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
to return NULL for non-NULL arguments. This is not the case as it can return NULL for invalid hexidecimal strings. Fixed by setting the maybe_null flag.
-
- 11 Jan, 2007 1 commit
-
-
evgen@moonbone.local authored
correctly. The Item_func::print method was used to print the Item_func_encode and the Item_func_decode objects. The last argument to ENCODE and DECODE functions is a plain C string and thus Item_func::print wasn't able to print it. The print() method is added to the Item_func_encode class. It correctly prints the Item_func_encode and the Item_func_decode objects.
-
- 23 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Changed header to GPL version 2 only
-
- 16 Nov, 2006 1 commit
-
-
kroki/tomash@moonlight.intranet authored
-
- 24 Aug, 2006 1 commit
-
-
kroki/tomash@moonlight.intranet authored
Changes in an item tree done by optimizer weren't properly registered and went unnoticed, which resulted in preliminary freeing of used memory.
-
- 11 Aug, 2006 1 commit
-
-
tsmith/tim@siva.hindu.god authored
Make the encryption functions MD5(), SHA1() and ENCRYPT() return binary results. Make MAKE_SET() and EXPORT_SET() use the correct character set for their default separator strings.
-
- 25 Jul, 2006 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
When executing INSERT over a view with calculated columns it was assuming all elements of the fields collection are actually Item_field instances. This may not be true when inserting into a view and that view has columns that are such expressions that allow updating (like setting a collation for example). Corrected to access field information through the filed_for_view_update() function and retrieve correctly the field info even for "update-friendly" non-Item_field items.
-
- 19 Jul, 2006 1 commit
-
-
igor@olga.mysql.com authored
for class Item_func_trim. For 4.1 it caused wrong output for EXPLAIN EXTENDED commands if expressions with the TRIM function of two arguments were used. For 5.0 it caused an error message when trying to select from a view with the TRIM function of two arguments. This unexpected error message was due to the fact that the print method for the class Item_func_trim was inherited from the class Item_func. Yet the TRIM function does not take a list of its arguments. Rather it takes the arguments in the form: [{BOTH | LEADING | TRAILING} [remstr] FROM] str) | [remstr FROM] str
-
- 11 Jul, 2006 1 commit
-
-
jimw@rama.(none) authored
The UNCOMPRESS() function was not marked as maybe_null, even though it returns NULL on invalid data. This confused the optimizer.
-
- 06 Jul, 2006 1 commit
-
-
igor@olga.mysql.com authored
The implementation of the method Item_func_reverse::val_str for the REVERSE function modified the argument of the function. This led to wrong results for expressions that contained REVERSE(ref) if ref occurred somewhere else in the expressions.
-
- 02 Jul, 2006 1 commit
-
-
kroki@mysql.com authored
invoker name The bug was fixed similar to how context switch is handled in Item_func_sp::execute_impl(): we store pointer to current Name_resolution_context in Item_func_current_user class, and use its Security_context in Item_func_current_user::fix_fields().
-
- 13 Jun, 2006 1 commit
-
-
ramil@mysql.com authored
-
- 06 Jun, 2006 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
mark result string using String::mark_as_const() which prevents CONCAT from reusing it as a buffer for concatenation result.
-
- 18 May, 2006 1 commit
-
-
jimw@mysql.com authored
The 'decimals' member of Item_func was being improperly initialized, which resulted in improper results when handling large numeric values.
-
- 14 Mar, 2006 1 commit
-
-
jimw@mysql.com authored
Results of string functions were being converted to decimals by first being converted to integers, resulting in a loss of precision.
-
- 06 Mar, 2006 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
calculate Item_func_format::max_length using charset->mbmaxlen
-
- 07 Dec, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Set max_length of Item_func_uuid to max_length*system_charset_info->mbmaxlen Note! Item_func_uuid should be set to use 'ascii' charset when hex(), format(), md5() etc will use 'ascii' - Comitting again, the old patch seems to have been lost.
-
- 21 Nov, 2005 1 commit
-
-
bar@mysql.com authored
item_strfunc.h, item_strfunc.cc, item.cc: Try to convert a const item into destination character set. If conversion happens without data loss, then cache the converted value and return it during val_str(). Otherwise, if conversion loses data, return Illeral mix of collations error, as it happened previously. ctype_recoding.result, ctype_recoding.test: Fixing tests accordingly.
-
- 10 Nov, 2005 1 commit
-
-
guilhem@mysql.com authored
"Item_date_add_interval needs to have the int_type member as Public". As explained in the bug report, this change is is to help http://search.cpan.org/~philips/DBIx-MyParse-0.20/ So please keep those members public.
-
- 07 Nov, 2005 1 commit
-
-
bar@mysql.com authored
ctype_utf8.result, ctype_utf8.test: Adding test case. item_strfunc.cc: item_strfunc.h: Moving the well formed checking code into a method, to reuse in several Item_func_xxx. Reusing the new method in Item_func_char and Item_func_charset_conv.
-
- 21 Oct, 2005 1 commit
-
-
bar@mysql.com authored
select distinct char(column) fails with utf8 ctype_utf8.result, ctype_utf8.test: Adding test case sql_yacc.yy: Adding new syntax. item_strfunc.h: Fixing wrong max_length calculation. Also, adding CHAR(x USING charset), for easier migrating from 4.1 to 5.0, according to Monty's suggestion.
-
- 13 Oct, 2005 1 commit
-
-
bar@mysql.com authored
New syntax: CHAR(x USING charset) Adding test case. sql_yacc.yy: New syntax: CHAR(x USING charset) Adding new parser rule. item_strfunc.h: New syntax: CHAR(x USING charset) Adding a new constructor.
-
- 11 Oct, 2005 1 commit
-
-
monty@mysql.com authored
- CHAR() now returns binary string as default - CHAR(X*65536+Y*256+Z) is now equal to CHAR(X,Y,Z) independent of the character set for CHAR() - Test for both ETIMEDOUT and ETIME from pthread_cond_timedwait() (Some old systems returns ETIME and it's safer to test for both values than to try to write a wrapper for each old system) - Fixed new introduced bug in NOT BETWEEN X and X - Ensure we call commit_by_xid or rollback_by_xid for all engines, even if one engine has failed - Use octet2hex() for all conversion of string to hex - Simplify and optimize code
-
- 15 Jul, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
correct value of CURRENT_USER() in SP with "security definer" (BUG#7291)
-
- 01 Jul, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 29 Jun, 2005 1 commit
-
-
igor@rurik.mysql.com authored
Added test cases for bug #11469. item_strfunc.h: Fixed bug #11469: wrong implementation of the not_null_tables method for CONCAT_WS.
-
- 23 Jun, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 17 Jun, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 06 Jun, 2005 1 commit
-
-
bar@mysql.com authored
UPPER/LOWER now can return a string with different length. mi_test1.c: Adding new arguments. Many files: Changeing caseup/casedn to return a result with different length than argument. sql_string.h: Removing unused method, mysql_priv.h: Removing unused method
-
- 17 May, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Set max_length of Item_func_uuid to max_length*system_charset_info->mbmaxlen Note! Item_func_uuid should be set to use 'ascii' charset when hex(), format(), md5() etc will use 'ascii'
-
- 10 May, 2005 2 commits
-
-
lenz@mysql.com authored
- removed an "#error PRAGMA" from sql/item_strfunc.h (msvensson) - Fixed BUG#10070 (range test failed if InnoDB is not available) (sergefp)
-
msvensson@neptunus.(none) authored
-
- 04 May, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Introduce ifdefs so we can control when to use #pragma interface on cygwin
-