- 29 Mar, 2008 3 commits
-
-
gkodinov/kgeorge@macbook.gmz authored
-
gkodinov/kgeorge@macbook.gmz authored
-
gkodinov/kgeorge@macbook.gmz authored
-
- 28 Mar, 2008 12 commits
-
-
iggy@amd64.(none) authored
into amd64.(none):/src/bug26243/my50-bug26243
-
anozdrin/alik@quad.opbmk authored
1. Use 'dat' extension, because it is handled in Makefile.am; 2. Fix typo: the bug id is 35469, not 35649.
-
iggy@amd64.(none) authored
into amd64.(none):/src/bug26243/my50-bug26243
-
anozdrin/alik@quad.opbmk authored
into quad.opbmk:/mnt/raid/alik/MySQL/devel/5.0-bt
-
iggy@amd64.(none) authored
- Backported the 5.1 DBUG to 5.0. - Avoid memory cleanup race on Windows client for CTRL-C
-
anozdrin/alik@quad.opbmk authored
The problem was that LOAD DATA code (sql_load.cc) didn't take into account that there may be items, representing references to other columns. This is a usual case in views. The crash happened because Item_direct_view_ref was casted to Item_user_var_as_out_param, which is not a base class. The fix is to 1) Handle references properly; 2) Ensure that an item is treated as a user variable only when it is a user variable indeed; 3) Report an error if LOAD DATA is used to load data into non-updatable column.
-
mattiasj@witty. authored
into witty.:/Users/mattiasj/clones/bug21413-50-bugteam
-
mattiasj@witty. authored
into witty.:/Users/mattiasj/clones/bug21413-50-engines
-
mattiasj@witty. authored
in REPLACE DELAYED post push patch, removing the optimization for copying delayed_insert variables.
-
evgen@moonbone.local authored
into moonbone.local:/work/27219-5.0-opt-mysql
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam
-
- 27 Mar, 2008 15 commits
-
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/mysql-5.0-opt
-
evgen@moonbone.local authored
Mixing aggregate functions and non-grouping columns is not allowed in the ONLY_FULL_GROUP_BY mode. However in some cases the error wasn't thrown because of insufficient check. In order to check more thoroughly the new algorithm employs a list of outer fields used in a sum function and a SELECT_LEX::full_group_by_flag. Each non-outer field checked to find out whether it's aggregated or not and the current select is marked accordingly. All outer fields that are used under an aggregate function are added to the Item_sum::outer_fields list and later checked by the Item_sum::check_sum_func function.
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
mattiasj@witty. authored
into witty.:/Users/mattiasj/clones/bug21413-50-engines
-
davi@mysql.com/endora.local authored
Fixed interference between tests: Users were added but not properly removed. This caused later tests to fail.
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.0-bugteam
-
df@pippilotta.erinye.com authored
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
tsmith@rhel5-ia64-a.mysql.com authored
into rhel5-ia64-a.mysql.com:/data0/tsmith/build/50
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/34731/50-34731
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/34731/50-34731
-
mattiasj@witty. authored
Bug#21413 "Engine table handler used by multiple threads in REPLACE DELAYED" When executing a REPLACE DELAYED statement, the storage engine ::extra() method was invoked by a different thread than the thread which has acquired the handler instance. This did not cause problems within the current server and with the current storage engines. But it has the potential to confuse future storage engines. Added code to avoid surplus calls to extra() method in case of DELAYED which avoids calling storage engine from a different thread than expected. No test case. This change does not change behavior in conjunction with current storage engines. So it cannot be tested by the regression test suite.
-
- 26 Mar, 2008 6 commits
-
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-opt
-
gshchepa/uchum@host.loc authored
View definition as SELECT ... FROM DUAL WHERE ... has valid syntax, but use of such view in SELECT or SHOW CREATE VIEW syntax causes unexpected syntax error. Server omits FROM DUAL clause when storing view body string in a .frm file for further evaluation. However, syntax of SELECT-witout-FROM query is more restrictive than SELECT FROM DUAL syntax, and doesn't allow the WHERE clause. NOTE: this syntax difference is not documented. View registration procedure has been modified to preserve original structure of view's body.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-build
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-
- 25 Mar, 2008 4 commits
-
-
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
Minor test case cleanup after bug#34529.
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
anozdrin/alik@quad.opbmk authored
into quad.opbmk:/mnt/raid/alik/MySQL/devel/5.0-rt-merged
-