- 04 Dec, 2006 1 commit
-
-
holyfoot/hf@deer.(none) authored
into mysql.com:/home/hf/work/22634/my51-22634
-
- 30 Nov, 2006 11 commits
-
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B11927-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
merge fix : removed undeterministic warnings
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.0-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.0-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
gkodinov/kgeorge@macbook.gmz authored
disabled warnings because their order is undeterministic
-
baker@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
-
kostja@bodhi.local authored
-
- 29 Nov, 2006 28 commits
-
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-4.1-runtime
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
kent@mysql.com/kent-amd64.(none) authored
Changed paths to ndb include directory to include "storage" Makefile.am: Adjusted path to yaSSL libtool libraries ssl.m4: Use libtool way of specifying yaSSL libraries
-
baker@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug20637
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-bug20637
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.0-opt
-
evgen@moonbone.local authored
Small fix for a test case
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.0-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.0-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.0-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-4.1-opt
-
gkodinov@dl145s.mysql.com authored
merged 5.0 testcases
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/mysql-5.1-build
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/mysql-5.1-build
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/mysql-5.1-build
-
kent@mysql.com/kent-amd64.(none) authored
into mysql.com:/home/kent/bk/mysql-5.0-build
-
kroki/tomash@moonlight.intranet authored
Note that we ignore CONCURRENT if LOAD DATA CONCURRENT is used from inside a stored routine and MySQL is compiled with Query Cache support (this is not in the manual). The problem was that the condition test of "we are inside stored routine" was reversed, thus CONCURRENT _worked only_ from stored routine. The solution is to use proper condition test. No test case is provided because the test case would require a large amount of input, and it's hard to tell is SELECT is really blocked or just slow (subject to race).
-