- 17 Dec, 2007 11 commits
-
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31752_/51-31752_
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/31752_/50-31752_
-
fix test program
-
build fixes
-
into mysql.com:/misc/mysql/31752_/51-31752_
-
into mysql.com:/misc/mysql/31752_/51-31752_
-
into mysql.com:/misc/mysql/31752_/50-31752_
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/32350/51-32350
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/32350/51-32350
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/misc/mysql/32350/50-32350
-
show version of mysqldump, release of server et al., and version of current server in mysqldumps.
-
- 15 Dec, 2007 1 commit
-
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32798-united/my51-bug32798-united-push
-
- 14 Dec, 2007 4 commits
-
-
mhansson/martin@linux-st28.site authored
a column with null values Post-merge fix
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32798-united/my51-bug32798-united
-
mhansson/martin@linux-st28.site authored
with null values For queries containing GROUP_CONCAT(DISTINCT fields ORDER BY fields), there was a limitation that the DISTINCT fields had to be the same as ORDER BY fields, owing to the fact that one single sorted tree was used for keeping track of tuples, ordering and uniqueness. Fixed by introducing a second structure to handle uniqueness so that the original structure has only to order the result.
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/my51-bug32858
-
- 13 Dec, 2007 18 commits
-
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/my51-bug32858
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug32858/my51-bug32858
-
sergefp@foxhole.(none) authored
into mysql.com:/home/psergey/mysql-5.0-bug32198
-
sergefp@mysql.com authored
- Make conditions like "date_col $CMP$ 'datetime-const'" range-sargable
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-opt
-
mhansson/martin@linux-st28.site authored
subselects into account It is forbidden to use the SELECT INTO construction inside UNION statements unless on the last SELECT of the union. The parser records whether it has seen INTO or not when parsing a UNION statement. But if the INTO was legally used in an outer query, an error is thrown if UNION is seen in a subquery. Fixed in 5.0 by remembering the nesting level of INTO tokens and mitigate the error unless it collides with the UNION.
-
- 12 Dec, 2007 2 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.1-axmrg
-
istruewing@stella.local authored
Fixed case of comment.
-
- 11 Dec, 2007 4 commits
-
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.1-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.1-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.1-axmrg
-
istruewing@stella.local authored
into stella.local:/home2/mydev/mysql-5.0-axmrg
-