An error occurred fetching the project authors.
- 27 Sep, 2006 2 commits
-
-
gkodinov/kgeorge@macbook.gmz authored
- fix moved to 5.1
-
gkodinov/kgeorge@macbook.gmz authored
- reversed the patch for 5.0 and moved to 5.1
-
- 14 Aug, 2006 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
optimizer does not honor IGNORE INDEX - Allow an index to be used for sorting the table instead of filesort only if it is not disabled by IGNORE INDEX.
-
- 21 Jul, 2006 1 commit
-
-
gkodinov/kgeorge@macbook.mshome.net authored
When making a place to store field values at the start of each group the real item (not the reference) must be used when deciding which column to copy.
-
- 31 Oct, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Cleanup of mysqltest.c before extending it
-
- 09 Sep, 2005 2 commits
-
-
serg@serg.mylan authored
-
sergefp@mysql.com authored
-
- 08 Sep, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 07 Aug, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 04 Aug, 2005 1 commit
-
-
evgen@moonbone.local authored
length. When temporary field created for DATE(LEFT(column,8)) expression, max_length value is taken from Item_date_typecast, and it is getting it from underlaid Item_func_left and it's max_length is 8 in given expression. And all this results in stripping last 2 digits. To Item_date_typecast class added its own fix_length_and_dec() function that sets max_length value to 10, which is proper for DATE field.
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 04 Jul, 2005 3 commits
-
-
monty@mysql.com authored
-
monty@mysql.com authored
- Mostly indentation fixes - Added missing test - Ensure that Item_func_case() checks for stack overruns - Use real_item() instead of (Item_ref*) item - Fixed wrong error handling
-
monty@mysql.com authored
Better fix for ON DUPLICATE KEY UPDATE
-
- 28 Jun, 2005 1 commit
-
-
igor@rurik.mysql.com authored
Added a test case for bug #11414. sql_select.cc: Fixed bug #11414: crash on Windows with some simple GROUP BY queries. It happened to an allocation of an array containing 0 Copy_field elements in setup_copy_fields. The bug had been already fixed in 5.0.
-
- 21 Jun, 2005 2 commits
-
-
igor@rurik.mysql.com authored
Correction for the test case of bug #11295 to remove warning.
-
igor@rurik.mysql.com authored
Added a test case for bug #11295. item_buff.cc: Fixed bug #11295. This a correction for the patch of bug #11088 that takes into account a possible NULL values of the BLOB column.
-
- 20 Jun, 2005 2 commits
-
-
igor@rurik.mysql.com authored
Added a test case for bug #11385. group_by.test: Added a test case for bug #11385. field.h: Fixed bug #11385. The bug was due to not defined method decimals for the class Field_datetime.
-
msvensson@neptunus.(none) authored
- Print warning that says display width is not supported for datatype TIMESTAMP, if user tries to create a TIMESTAMP column with display width. - Use display width for TIMESTAMP only in type_timestamp test to make sure warning is displayed correctly.
-
- 16 Jun, 2005 3 commits
-
-
igor@rurik.mysql.com authored
Correction after merge of fix for bug #8614.
-
igor@rurik.mysql.com authored
Added a test case for bug #8614. sql_select.cc: Fixed bug #8614. SELECT DISTINCT ... GROUP BY 'const' must be equivalent to SELECT ... GROUP BY 'const'.
-
timour@mysql.com authored
Exclude the query that generates warning from PS tests, due to extra warning under PS.
-
- 15 Jun, 2005 1 commit
-
-
timour@mysql.com authored
When the GROUP BY clause contains a column reference that can be resolved to both an aliased column in the SELECT list, and to a column in the FROM clause, the group column is resolved to the column in the FROM clause (for ANSI conformance). However, it may be so that the user's intent is just the other way around, and he/she gets the query results grouped by a completely different column than expexted. This patch adds a warning in such cases that tells the user that there is potential ambiguity in the group column. sql/sql_select.cc - Added a warning when a GROUP column is ambiguous due to that there is a column reference with the same name both in the SELECT and FROM clauses. In this case we resolve to the column in FROM clause and warn the user of a possible ambiguity. - More extensive comments. - Changed the function to return bool instead of int (as in other places). mysql-test/t/group_by.test Added test for BUG#11211. mysql-test/r/group_by.result Added test for BUG#11211.
-
- 07 Jun, 2005 1 commit
-
-
igor@rurik.mysql.com authored
Fixed bug #11088: a crash for queries with GROUP BY a BLOB column + COUNT(DISTINCT...) due to an attempt to allocate a too large buffer for the BLOB field. Now the size of the buffer is limited by max_sort_length. group_by.test, group_by.result: Added a test case for bug #11088.
-
- 18 Apr, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 31 Mar, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 30 Mar, 2005 1 commit
-
-
sergefp@mysql.com authored
Make test_if_skip_sort_order() rebuild tab->ref if it decides to use an index different from the index join optimizer has choosen.
-
- 15 Feb, 2005 1 commit
-
-
monty@mysql.com authored
This fixes also the reverse lookup bug introduced by the previous patch
-
- 08 Feb, 2005 1 commit
-
-
monty@mysql.com authored
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()
-
- 07 Feb, 2005 1 commit
-
-
monty@mysql.com authored
(BUG 8216)
-
- 11 Dec, 2004 1 commit
-
-
sergefp@mysql.com authored
In Item_ref::Item_ref set maybe_null (and other fields fix_fields sets) to be the same as in (*ref), because Item_ref::fix_fields() will not be called. Previously maybe_null was 0 always and this produced a bogus state where maybe_null==0 && is_null() == true which broke evaluation for some upper-level Items, like AND and OR.
-
- 08 Sep, 2004 1 commit
-
-
sergefp@mysql.com authored
Don't evaluate the value of GROUP_CONCAT several times for the same 'group', reuse the value instead.
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 09 Dec, 2003 2 commits
-
-
konstantin@mysql.com authored
--disable_query_log was not a good idea, Serg says
-
konstantin@mysql.com 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)
-
- 18 Aug, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Use server character set if --default-character-set is not used Added convert_string() for more efficient alloc+character-set convert of strings
-
- 09 Jul, 2003 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
-
- 23 Apr, 2003 2 commits
-
-
monty@narttu.mysql.fi authored
(There was a problem on some AMD system when the floating point precision wasn't accurate enough)
-
monty@narttu.mysql.fi authored
Added optimzation for clustered index Fixed bug in UPDATE ... ORDER BY Fixed handling of UPDATE ... LIMIT
-