- 12 May, 2006 14 commits
-
-
gluh@eagle.intranet.mysql.r18.ru authored
replaced get_field(MEM_ROOT *mem, Field *field) with get_field(MEM_ROOT *mem, Field *field, String *res). It allows to avoid strlen().
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
tnurnberg@mysql.com authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
gluh@eagle.intranet.mysql.r18.ru authored
-
msvensson@neptunus.(none) authored
-
tnurnberg@mysql.com authored
into mysql.com:/home/mysql-5.0-10418
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
- Don't kill the active connection to the server, instead read the connection id, switch connection and kill the first one from there.
-
igor@rurik.mysql.com authored
a worse execution plan than in 4.1 for some queries. It happened due the fact that at some conditions the optimizer always preferred range or full index scan access methods to lookup access methods even when the latter were much cheaper. The problem was not observed in 4.1 for the reported query because the WHERE condition was not of a form that could cause the problem. Equality propagation introduced on 5.0 added an extra predicate and changed the WHERE condition. The new condition provoked the optimizer to make a bad choice. The problem was fixed by the patch for bug 17379.
-
- 11 May, 2006 2 commits
-
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/mysql-5.0-maint
-
tnurnberg@mysql.com authored
into mysql.com:/home/mysql-4.1-10418
-
- 10 May, 2006 14 commits
-
-
tnurnberg@mysql.com authored
into mysql.com:/home/mysql-5.0-19263
-
kent@mysql.com authored
-
kent@mysql.com authored
Compile in all character sets in Max (bug#14918)
-
ramil@production.mysql.com authored
into production.mysql.com:/usersnfs/rkalimullin/mysql-5.0
-
ramil@production.mysql.com authored
into production.mysql.com:/usersnfs/rkalimullin/mysql-5.0
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/mysql-5.0__bug19564
-
sergefp@mysql.com authored
Re-work best_access_path() and find_best() to reuse E(#rows(range access)) as E(#rows(ref[_or_null](const) access) only when it is appropriate. [This is the final cumulative patch]
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/mysql-5.0
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/mysql-5.0__bug19564
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/4.1.b18501
-
gkodinov@mysql.com authored
into mysql.com:/home/kgeorge/mysql/5.0/B18068
-
cmiller@zippy.(none) authored
Correct a bug (that I introduced, after using Oracle's database software for too many years) where the length of the database-sent data is incorrectly used to infer NULLness.
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-best_access_path_j-push
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-best_access_path_j-push
-
- 09 May, 2006 10 commits
-
-
acurtis@xiphis.org authored
into xiphis.org:/home/antony/work2/mysql-5.0-engines-merge
-
acurtis@xiphis.org authored
into xiphis.org:/home/antony/work2/p1-bug10952.1
-
acurtis@xiphis.org authored
"alter table from MyISAM to MERGE lost data without errors and warnings" Add new handlerton flag which prevent user from altering table storage engine to storage engines which would lose data. Both 'blackhole' and 'merge' are marked with the new flag. Tests included.
-
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.0-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
mskold@mysql.com authored
into mysql.com:/home/marty/MySQL/mysql-5.0
-
mskold@mysql.com authored
into mysql.com:/home/marty/MySQL/mysql-5.0
-
mskold@mysql.com authored
-
msvensson@neptunus.(none) authored
- Add a check to see if the .mysql_history file a symlink to /dev/null and in such case, skip reading and writing to it.
-