mariadb

Tree: 2220fe2774

Author	SHA1	Message	Date
evgen@moonbone.local	fc0e206cb5	Bug#23409: Arguments of the ENCODE() and the DECODE() functions were not printed 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.	19 years ago
ramil/ram@mysql.com/myoffice.izhnet.ru	31402835d4	Fix for bug #23254 : COMPRESS(NULL) makes all futher COMPRESS() calls on same Item return NULL We don't set null_value to 0 in the Item_func_compress::val_str() for not-NULL results.	20 years ago
ramil/ram@mysql.com/myoffice.izhnet.ru	d3f503a0bd	Fix for bug #20204 : "order by" changes the results returned Item_substr's results are improperly stored in a temporary table due to wrongly calculated max_length value for multi-byte charsets if two arguments specified.	20 years ago
tsmith/tim@siva.hindu.god	45460bd0af	Bug #21531 : EXPORT_SET() doesn't accept args with coercible character sets - Fix typo in Item_func_export_set::fix_length_and_dec() which caused character set aggregation to fail - Remove default argument from last arg of agg_arg_charsets() function, to reduce potential errors	20 years ago
tsmith/tim@siva.hindu.god	72d55f3878	Bug #20536 : md5() with GROUP BY and UCS2 return different results on myisam/innodb 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.	20 years ago
igor@olga.mysql.com	f201828dd8	Fixed bug #17526 : incorrect print method 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	20 years ago
igor@olga.mysql.com	0e3d2dafd6	Fixed bug #18243 . 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.	20 years ago
cmiller@zippy.(none)	5039184e83	Bug#19006: 4.0 valgrind problems (in test func_str) On exactly-sized Strings, the String::c_ptr() function peeked beyond the end of the buffer, possibly into unititialized space to see whether the buffer was NUL-terminated. In a place that did peek improperly, we now use a c_ptr_safe() function, which doesn't peek where it shouldn't.	20 years ago
evgen@moonbone.local	b8b9738e0b	item_strfunc.cc: Fix for bug#16716 for --ps-protocol mode. item_cmpfunc.cc: Fix for a memory allocation/freeing problem in agg_cmp_type() after fix for bug#16377. Few language corrections.	20 years ago
ramil@mysql.com	97562d74c9	Fix for bug #12728 : Very strange behaviour of ELT	20 years ago
evgen@moonbone.local	766b4a8c7f	Fixed bug#15351: Wrong collation used for comparison of md5() and sha() argument can lead to a wrong result. md5() and sha() functions treat their arguments as case sensitive strings. But when they are compared their arguments were compared as a case insensitive strings which leads to two functions with different arguments and thus different results to being identical. This can lead to a wrong decision made in the range optimizer and thus lead to a wrong result set. Item_func_md5::fix_length_and_dec() and Item_func_sha::fix_length_and_dec() functions now set binary collation on their arguments.	20 years ago
evgen@moonbone.local	40ea30253f	Fixed bug#16716: subselect in concat() may lead to a wrong result. The Item_func_concat::val_str() function tries to make as less re-allocations as possible. This results in appending strings returned by 2nd and next arguments to the string returned by 1st argument if the buffer for the first argument has enough free space. A constant subselect is evaluated only once and its result is stored in an Item_cache_str. In the case when the first argument of the concat() function is such a subselect Item_cache_str returns the stored value and Item_func_concat::val_str() append values of other arguments to it. But for the next row the value in the Item_cache_str isn't restored because the subselect is a constant one and it isn't evaluated second time. This results in appending string values of 2nd and next arguments to the result of the previous Item_func_concat::val_str() call. The Item_func_concat::val_str() function now checks whether the first argument is a constant one and if so it doesn't append values of 2nd and next arguments to the string value returned by it.	20 years ago
tnurnberg@mysql.com	21f4e8aadb	Bug#10418: LOAD_FILE does not behave like in manual if file does not exist load_file() string-function should return NULL rather than throw an error if the file doesn't exist, as per the manual.	20 years ago
ramil@mysql.com	2398882097	Fix for bug #18643 : crazy UNCOMPRESS().	20 years ago
konstantin@mysql.com	9105d06dd6	A fix for Bug#13944 "libmysqlclient exporting sha1_result function": rename sha1_* to mysql_sha1_*	20 years ago
bar@mysql.com	2f72e05903	Bug#10446 Illegal mix of collations: 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.	20 years ago
jimw@mysql.com	77fbc72f47	Handle errors returned by system crypt() in ENCRYPT(). (Bug #13619 )	21 years ago
jimw@mysql.com	663d0bbdfb	Fix crash in DES_DECRYPT(NULL). (Bug #12757 )	21 years ago
patg@krsna.patg.net	6128521b5b	item_strfunc.cc: BUG #11104 Took out the offset-=delimiter_length-1 out of the for loop. It was causing basically this: select substring_index('the king of the the hill', 'the', -2) to not work. The first iteration, offset would be initialised to 24, then strstr would point at 'the king of the the* hill' (''means right before the character following), returning a offset of 16. The for loop would then decrement offset by two (3 - 1), to 14, now pointing at "the king of the the hill", _skipping_ past the 'e' in the second to last 'the', and therefore strstr would never have a chance of matching the second to last 'the', then moving on to the 'the' at the begginning of the string! In a nutshell, offset was being decremented by too great a value, preventing the second to last 'the' from being ever found, hence the result of 'king of the the hill' from the query that is reported in the bug report func_str.test: BUG #11104 Added tests to make sure fix addresses issues in original bug report func_str.result: BUG #11104 New results for new tests	21 years ago
bar@mysql.com	e6f96b4939	func_system.result, func_system.test: adding test case item_strfunc.cc: Bug#12351 CONCAT with USER()/DATEBASE() and a column gets strange results. Mark created Item_str as constant, so CONCAT cannot reuse it for optimization purposes.	21 years ago
patg@krsna.patg.net	8109934e1d	BUG 11104 (same as changeset 1.1891 on the 5.0 tree, but realised this needed to be fixed in earlier versions) Fixed the iteration of how substrings are handled with negative indexes in SUBSTRING_INDEX	21 years ago
jimw@mysql.com	e26a344d19	Fix calculation for length of LPAD() and RPAD() reported to client via mysql_fetch_fields(). (Bug #11311)	21 years ago
monty@mishka.local	7e83d09ce7	Simple fixes during review of new code	21 years ago
gluh@eagle.intranet.mysql.r18.ru	672e1f20cb	Bug #9854 hex() and out of range handling added out of range handling	21 years ago
jimw@mysql.com	de9909faec	Fix crash caused by calling DES_ENCRYPT() without the --des-key-file option having been passed to the server. (Bug #11643)	21 years ago
bell@sanja.is.com.ua	0e30eea141	fixed substring() length calculation in case of constant negative argument (BUG#10269)	21 years ago
monty@mishka.local	7398252d02	Portability fixes Fixes while reviewing new pushed code NULL as argument to encrypt/decrypt should return NULL without a warning	21 years ago
msvensson@neptunus.(none)	daba295db0	BUG#10589: des_encrypt functionality always return NULL - Push warnings if des_encrypt or des_descrypt function fails because of out of resources or wrong params. - Push warning if des_encrypt or des_decrypt function is used when server is missing support for openssl. - Add test func_encrypt_nossl that is tun when the server is missing support for openssl.	21 years ago
serg@serg.mylan	6a5349028c	a compiler must see '#pragma implementation' before '#pragma interface' (that comes with the #include'd header file)	21 years ago
monty@mysql.com	29fd1f2fd9	Move USE_PRAGMA_IMPLEMENTATION to proper place 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	21 years ago
kent@mysql.com	bd48eed988	tztime.cc: Set #pragma implementation" earlier Many files: Need to include <my_global.h> before #ifdef USE_PRAGMA_IMPLEMENTATION	21 years ago
msvensson@neptunus.(none)	83d430353e	Add ifdefs to control when "#pragma implementation" should be used Added some more ifdefs for "#pragma interface"	21 years ago
bar@noter.(none)	c783cb3d7e	SUBSTR with negative argument didn't work with multi-byte strings, length() instead of numchars() where used in a mistake.	21 years ago
bar@mysql.com	a7b877df78	Bugs#9129: CHARSET(), COLLATION(), COERCIBILITY() not always correct for NULL values. Now they always result a non NULL value even the argument is NULL. It is more usefull for debugging purposes.	21 years ago
bar@mysql.com	c6c887b990	# Bug#8785 Problem with nested concats and character set conversion of a string constant.	21 years ago
igor@rurik.mysql.com	4559fb998b	func_str.result, func_str.test: Added a test case for bug #8669. item_strfunc.cc: Fixed bug #8669. Function AES_DECRYPT can return NULL value.	21 years ago
gluh@gluh.mysql.r18.ru	00449b8f9c	Fix for bug#8978 : Crash on 'select format ...'	21 years ago
bar@mysql.com	7e8e033290	type_blob.result, func_system.result, func_str.result, ctype_collate.result: fixing test results accordingly. func_system.test: New test that illegal mix of collations does not happen anymore. item_strfunc.h: safe_charset_converter() was added for system constants. item_strfunc.cc: safe_charset_converter() was added for system constants. item_func.cc, item.h, item.cc: Bug#8291: Illegal collation mix with USER() function. After discussion with PeterG and Serge, a new coercibility level for "system constants" was introduced, between COERRIBLE and IMPLICIT. Thus: SELECT col1 = USER() FROM t1; - is done according to col1 collation. SELECT 'string' = USER(); - is done according to USER() collation. At the same time, "nagg" and "strong" members were removed as unused. item_create.cc: Version is a system constant too.	21 years ago
gluh@gluh.mysql.r18.ru	2b5ee94a33	Fix for bug#6317: string function CHAR, parameter is NULL, wrong result	21 years ago
monty@mysql.com	e2dc9b4099	Backport my_strntod() from 5.0 Change string->float conversion to delay division as long as possible. This gives us more exact integer->float conversion for numbers of type '123.45E+02' (Bug #7740)	21 years ago
ramil@mysql.com	9a042c81e7	A fix. "(int) var" type cast doesn't work correctly for uint32 var on some 64-bit platforms (e.g. IRIX, non-debug build).	21 years ago
monty@mysql.com	79ec81071a	Better bugfix for "HAVING when refering to RAND()" (Bug #8216 ) Ensure that references in HAVING, ORDER BY or GROUP BY are calculated after fields in SELECT. This will ensure that any reference to these has a valid value. Generalized the code for split_sum_func()	21 years ago
monty@mysql.com	32f91f48e8	Fixed bug in HAVING when refering to RAND() through alias (BUG 8216)	21 years ago
igor@rurik.mysql.com	0fb0dab4ca	func_str.result, func_str.test: Added a test case for bug #7751. item_strfunc.cc: Fixed bug #7751. The function Item_func_conv::val_str did not update the unsigned_flag value.	21 years ago
jimw@mysql.com	e86457cef0	Fix QUOTE() to not reuse the input field for output, which resulted in incorrect results when the input was a constant across a multi-row SELECT statement. (Bug #8248)	21 years ago
serg@serg.mylan	67ba2e367a	fixes/cleanups according to Coverity report	21 years ago
bar@mysql.com	8f23e90232	#7874 : CONCAT() gives wrong results mixing latin1 field and utf8 string literals We should not overwrite res if it is returned from a const item.	21 years ago
bar@mysql.com	e7e5e8b1e7	user_var.result, func_str.result, item_strfunc.cc: bug#7839 ncorrect collation for char(ascii('a'))	21 years ago
bar@mysql.com	2bd854c859	Bug #7730 Server crash using soundex on an utf8 table Don't use my_tolower: it works only for 8bit charsets.	21 years ago
timour@mysql.com	064c73490b	Fix for BUG#7455. The fix checks if the trim string argument is NULL. If so, the standard mandates that the function result must be also NULL.	21 years ago

1 2 3 4 5 ...

403 Commits (2220fe2774bf2b041ba9894e33d23d2bf03a5df1)