An error occurred fetching the project authors.
- 02 Jun, 2009 1 commit
-
-
Sergey Glukhov authored
The crash happens due to wrong max_length value which is set on Item_func_round::fix_length_and_dec() stage. The value is set to args[0]->max_length which is too big in case of LONGTEXT(LONGBLOB) fields. The fix is to set max_length using float_length() function.
-
- 23 Feb, 2009 1 commit
-
-
Alexey Kopytov authored
Both of our own implementations of rint(3) were inconsistent with the most common behavior of rint() on those platforms that have it: round to nearest, break ties by rounding to nearest even. Fixed by leaving just one implementation of rint() in our source tree, and changing its behavior to match the most common native implementations on other platforms.
-
- 28 Jan, 2009 1 commit
-
-
Alexey Kopytov authored
Various parts of code used different 'precision' arguments for sprintf("%g") when converting floating point numbers to a string. This led to differences in results in some cases depending on whether the text-based or prepared statements protocol is used for a query. Fixed by changing arguments to sprintf("%g") to always be 15 (DBL_DIG) so that results are consistent regardless of the protocol. This patch will be null-merged to 6.0 as the problem does not exists there (fixed by the patch for WL#2934).
-
- 01 Oct, 2007 2 commits
-
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
-
- 28 Sep, 2007 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
When calculating the result length of an integer DIV function the number of decimals was used without checking the result type first. Thus an uninitialized number of decimals was used for some types. This caused an excessive amount of memory to be allocated for the field's buffer and crashed the server. Fixed by using the number of decimals only for data types that can have decimals and thus have valid decimals number.
-
- 28 Apr, 2007 1 commit
-
-
kaa@polly.local authored
Fix for bug #24912 "problems with bigint in abs() ceiling() round() truncate() mod()" and a number of related problems: - unsigned flag was not handled correctly for a number of mathematical funcions, which led to incorrect results - passing large values as the number of decimals to ROUND() resulted in incorrect results and even server crashes in some cases - reverted the fix and the testcase for bug #10083 as it violates the manual - fixed some testcases which relied on broken ROUND() behavior
-
- 27 Jun, 2006 1 commit
-
-
kroki@mysql.com authored
The problem was that we restored SQL_CACHE, SQL_NO_CACHE flags in SELECT statement from internal structures based on value set later at runtime, not the original value set by the user. The solution is to remember that original value.
-
- 06 Mar, 2006 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
calculate Item_func_format::max_length using charset->mbmaxlen
-
- 07 Feb, 2006 1 commit
-
-
gunnar@mysql.com. authored
fix for bug#8461 BUG 8461 - TRUNCATE returns incorrect result if 2nd argument is negative Reason: Both TRUNCATE/ROUND converts INTEGERS to DOUBLE and back to INTEGERS Changed the integer routine to work on integers only. This bug affects 4.1, 5.0 and 5.1 Fixing in 4.1 will need to change the routine to handle different types individually. 5.0 did had different routines for different types already just the INTEGER routine was bad.
-
- 18 Oct, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 17 Oct, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 06 Sep, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
Argument of RAND function can be constant value only
-
- 02 Aug, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 23 Jun, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 15 Jun, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 09 Jun, 2005 1 commit
-
-
holyfoot@hf-ibm.(none) authored
-
- 08 Jun, 2005 1 commit
-
-
holyfoot@hf-ibm.(none) authored
-
- 19 May, 2005 1 commit
-
-
ramil@mysql.com authored
we need proper rounding there
-
- 27 Apr, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 19 Apr, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 20 Dec, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 19 Aug, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 11 Aug, 2004 1 commit
-
-
lenz@mysql.com authored
format() around them (as suggested by serg)
-
- 31 Jul, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 13 May, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 19 Mar, 2004 1 commit
-
-
monty@mysql.com authored
Fixed some wrong column specifications in mysql_fix_privilege_tables
-
- 12 Mar, 2004 1 commit
-
-
monty@mysql.com authored
-
- 04 Mar, 2004 1 commit
-
-
vva@eagle.mysql.r18.ru authored
-
- 06 Feb, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 13 Jan, 2004 1 commit
-
-
vva@eagle.mysql.r18.ru authored
by fixing optimizer bug with help of 'volatile' keyword
-
- 31 Oct, 2003 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 30 Oct, 2003 1 commit
-
-
bell@sanja.is.com.ua authored
added code covarage for functions convert(), nullif(), crc32(), is_used_lock(), char_lengtrh(), bit_xor() added string length for more speed made code covarage for print() method of Item fixed printability of some items (SCRUM) (WL#1274)
-
- 27 Jan, 2003 1 commit
-
-
serg@serg.mysql.com authored
and VERSION() to be uppercase in e.g. "select pi()"
-
- 03 Dec, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Optimized SELECT DISTINCT ... ORDER BY ... LIMIT Fixed reference to uninitalized variable
-
- 17 Jul, 2002 1 commit
-
-
peter@mysql.com authored
-
- 04 Jun, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Fixes after last merge from 4.0. (Code not yet complete, need anoter merge from 4.0)
-
- 03 Jun, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Added syntax for column comments (for compability with 4.1) Fix of ALTER TABLE RENAME
-
- 31 May, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Change TRUNCATE(number) to truncate towards zero for negative numbers Fix NULL handling for DESCRIBE table_name
-
- 22 Nov, 2001 1 commit
-
-
monty@hundin.mysql.fi authored
LOCATE() is now case sensitive
-