An error occurred fetching the project authors.
- 06 Jun, 2006 1 commit
-
-
evgen@moonbone.local authored
To calculate its max_length the CONCAT() function is simply sums max_lengths of its arguments but when the collation of an argument differs from the collation of the CONCAT() max_length will be wrong. This may lead to a data truncation when a tmp table is used, in UNIONS for example. The Item_func_concat::fix_length_and_dec() function now recalculates the max_length of an argument when the mbmaxlen of the argument differs from the mbmaxlen of the CONCAT().
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 02 Jan, 2005 1 commit
-
-
sergefp@mysql.com authored
(this depends on s[n]printf implementation and differs from system to system)
-
- 30 Dec, 2004 1 commit
-
-
sergefp@mysql.com authored
-
- 17 Dec, 2004 1 commit
-
-
sergefp@mysql.com authored
For numeric constants we only need to add, since the parser doesn't produce negative numbers. For strings we only add (we actually could substract 1 if given string is a constant and it has '-number' form but we're not doing that because * we set max_length bigger then necessary in other cases as well. * the current solution is simpler and safer (bigger max_length is better then cutting out)
-
- 15 Sep, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 05 Jan, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Cleaned up test; Removed wrong DROP TABLE commands and use standard table and database names. changed store_warning() -> push_warning_print()
-
- 17 May, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Update of glibc patch from MySQL 4.0
-