- 12 May, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
- 11 May, 2006 12 commits
-
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.1-merge6
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.1-merge6
-
tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/51/a.bug6061
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.1-merge6
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.1-merge6
-
sergefp@mysql.com authored
-
reggie@big_geek. authored
bringing handlerton-win.cc back after incorrectly deleteing it. It is not needed for 5.1 or later but is used by 5.0
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.1-merge5
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.1-merge5
-
jmiller@mysql.com authored
into mysql.com:/home/ndbdev/jmiller/clones/mysql-5.1-new
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/51/a.bug6061
-
- 10 May, 2006 21 commits
-
-
jmiller@mysql.com authored
into mysql.com:/home/ndbdev/jmiller/clones/mysql-5.1-new
-
jmiller@mysql.com authored
Remove comments not needed
-
jmiller@mysql.com authored
Correct fix for test bug #19158
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/51/a.bug6061
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
serg@sergbook.mysql.com authored
by a dirty word, and it complains about it, even in a comment.
-
tim@siva.hindu.god authored
- Fix mysqld_safe so that it always passes correct --log-error argument to mysqld - A few other minor clean-ups to mysqld_safe
-
joerg@mysql.com authored
-
joerg@mysql.com authored
into mysql.com:/M51/mysql-5.1
-
serg@sergbook.mysql.com authored
into sergbook.mysql.com:/usr/home/serg/Abk/mysql-5.1
-
joerg@mysql.com authored
-
serg@sergbook.mysql.com authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
joerg@mysql.com authored
into mysql.com:/M51/mysql-5.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
- 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.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1
-
midom@flute.local authored
-