- 10 May, 2006 2 commits
-
-
serg@sergbook.mysql.com authored
into sergbook.mysql.com:/usr/home/serg/Abk/mysql-5.1
-
serg@sergbook.mysql.com authored
-
- 09 May, 2006 6 commits
-
-
serg@sergbook.mysql.com authored
-
gkodinov@mysql.com authored
into mysql.com:/home/kgeorge/mysql/5.1/B18068
-
serg@sergbook.mysql.com authored
-
gkodinov@mysql.com authored
When converting DISTINCT to GROUP BY where the columns are from the covering index and they are quoted twice in the SELECT list the optimizer is creating improper processing sequence. This is because of the fact that the columns of the covering index are not recognized as such and treated as non-index columns. Generally speaking duplicate columns can safely be removed from the GROUP BY/DISTINCT list because this will not add or remove new rows in the resulting set. Duplicates can be removed even if they are not consecutive (as is the case for ORDER BY, where the duplicate columns can be removed only if they are consecutive). So we can safely transform "SELECT DISTINCT a,a FROM ... ORDER BY a" to "SELECT a,a FROM ... GROUP BY a ORDER BY a" instead of "SELECT a,a FROM .. GROUP BY a,a ORDER BY a". We can even transform "SELECT DISTINCT a,b,a FROM ... ORDER BY a,b" to "SELECT a,b,a FROM ... GROUP BY a,b ORDER BY a,b". The fix to this bug consists of checking for duplicate columns in the SELECT list when constructing the GROUP BY list in transforming DISTINCT to GROUP BY and skipping the ones that are already in.
-
midom@flute.local authored
-
mskold@mysql.com authored
-
- 08 May, 2006 11 commits
-
-
serg@sergbook.mysql.com authored
-
serg@sergbook.mysql.com authored
-
serg@sergbook.mysql.com authored
-
serg@sergbook.mysql.com authored
autotool-ize plugins before the main source tree
-
serg@sergbook.mysql.com authored
-
serg@sergbook.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
-
tomas@poseidon.ndb.mysql.com authored
-
mskold@mysql.com authored
into mysql.com:/home/marty/MySQL/mysql-5.1-new
-
- 06 May, 2006 3 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new
-
serg@sergbook.mysql.com authored
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.1-bug10405
-
- 05 May, 2006 10 commits
-
-
tomas@poseidon.ndb.mysql.com authored
- ndb system tables not created because of filter, moved chack of filter
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1
-
monty@mysql.com authored
(Fixes core dump in rpl_failed_optimize.test) Ensure we end active transcations if we do an admin command (like optimize, repair etc)
-
jmiller@mysql.com authored
into mysql.com:/home/ndbdev/jmiller/clones/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
fixed memleak in ndbcluster_end
-
mskold@mysql.com authored
Bug #18798: mysqld cores on update in ha_ndbcluster call if cluster has failed before, added extra check that transaction is started
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.1
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.1-bug10405
-
monty@mysql.com authored
-
- 04 May, 2006 8 commits
-
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
-
serg@sergbook.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
-
monty@mysql.com authored
-