- 25 Mar, 2008 6 commits
-
-
malff@lambda.hsd1.co.comcast.net. authored
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.1-8759
-
malff@lambda.hsd1.co.comcast.net. authored
-
malff@lambda.hsd1.co.comcast.net. authored
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.1-opt-merge
-
malff@lambda.hsd1.co.comcast.net. authored
instructions) This bug can not be reproduced in the current version, adding the test case to the test suite for coverage, no code change.
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.1-opt
-
gshchepa/uchum@host.loc authored
Minor test case cleanup after bug#34529.
-
- 24 Mar, 2008 2 commits
-
-
mhansson/autopush@riffraff.(none) authored
into riffraff.(none):/data0/autopush/my50-bug34529
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/warnings-5.1-opt
-
- 23 Mar, 2008 5 commits
-
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/33334/my51-33334
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/33334/my51-33334
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/33334/my50-33334
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/33334/my51-33334
-
gkodinov/kgeorge@macbook.gmz authored
-
- 21 Mar, 2008 4 commits
-
-
malff@lambda.hsd1.co.comcast.net. authored
Fixed the parser to reject SQLSTATE '00000', since '00000' is the successful completion condition, and can not be caught by an exception handler in SQL.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B26461-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B26461-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
The bool data type was redefined to BOOL (4 bytes on windows). Removed the #define and fixed some of the warnings that were uncovered by this. Note that the fix also disables 2 warnings : 4800 : 'type' : forcing value to bool 'true' or 'false' (performance warning) 4805: 'operation' : unsafe mix of type 'type' and type 'type' in operation These warnings will be handled in a separate bug, as they are performance related or bogus. Fixed to int the return type of functions that return more than 2 distinct values.
-
- 19 Mar, 2008 10 commits
-
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.1-opt
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.1-opt
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
mhansson/martin@riffraff.(none) authored
When swapping out heap I_S tables to disk, this is done after plan refinement. Thus, READ_RECORD::file will still point to the (deleted) heap handler at start of execution. This causes segmentation fault if join buffering is used and the query is a star query where the result is found to be empty before accessing some table. In this case that table has not been initialized (i.e. had its READ_RECORD re-initialized) before the cleanup routine tries to close the handler. Fixed by updating READ_RECORD::file when changing handler.
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.0-opt
-
holyfoot/hf@mysql.com/hfmain.(none) authored
Before breaking the connection we have to check that there's no query executing at the moment. Otherwise it can lead to crash in embedded server.
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/bug34512/my51
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
- 18 Mar, 2008 1 commit
-
-
gluh@mysql.com/mgluh.(none) authored
added intialization of f_key_info.referenced_key_name for the case when referenced table is dropped
-
- 14 Mar, 2008 2 commits
-
-
gshchepa/uchum@host.loc authored
Queries like: SELECT ROW(1, 2) IN (SELECT t1.a, 2) FROM t1 GROUP BY t1.a or SELECT ROW(1, 2) IN (SELECT t1.a, 2 FROM t2) FROM t1 GROUP BY t1.a lead to assertion failure in the Item_in_subselect::row_value_transformer method in debugging build, or to unexpected error message in release build: ERROR 1247 (42S22): Reference '<list ref>' not supported (forward reference in item list) Unexpected error message and assertion failure have been eliminated.
-
gluh@mysql.com/eagle.(none) authored
referenced_key_name field can be uninitialized in the case when referenced table is dropped. Added codition which allows to handle this situation.
-
- 13 Mar, 2008 2 commits
-
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
Disable test case for bug 29948, which is causing sporadically failures in other tests inside mysql_client_test.
-
- 12 Mar, 2008 8 commits
-
-
kaa@kaamos.(none) authored
bug12713.
-
ssh://bk-internal.mysql.com//home/bk/mysql-5.1-optkaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
-
kaa@kaamos.(none) authored
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.1-opt
-
kaa@kaamos.(none) authored
into kaamos.(none):/data/src/opt/mysql-5.0-opt
-