- 02 Aug, 2006 4 commits
-
-
mikael/pappa@dator5.(none) authored
ascii on varchar now allowed
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/bug18198
-
joerg@trift2. authored
into trift2.:/M51/merge-5.0-to-5.1
-
mikael/pappa@dator5.(none) authored
New methods to handle VARCHAR strings and CHAR's which are not using a binary collation. Indentation fixes Now strings are run through strnxfrm before they are processed by the partition function We do not allow collations where strnxfrm expands the string since we want the resulting string to fit in the same value range as the original.
-
- 01 Aug, 2006 15 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
-
evgen@sunlight.local authored
After merge fix
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
-
evgen@sunlight.local authored
After merge fix
-
evgen@sunlight.local authored
After merge fix
-
gkodinov/kgeorge@macbook.gmz authored
-
gkodinov/kgeorge@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/B20103-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
- make the client to respect the server-side no_backslash_escapes option and disable the special meaning of backslash also at client side.
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
-
evgen@sunlight.local authored
-
gkodinov/kgeorge@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/B11551-5.0-opt
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.0-opt-mysql
-
lars/lthalmann@dl145k.mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
- 31 Jul, 2006 13 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
-
lars/lthalmann@dl145j.mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-4.1-merge
-
evgen@moonbone.local authored
After merge fix
-
sergefp@mysql.com authored
-
gkodinov/kgeorge@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/B11551-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
made DROP VIEW to continue on error and report an aggregated error at its end. This makes it similar to DROP TABLE.
-
mikael/pappa@dator5.(none) authored
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B21080-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
When executing ALTER TABLE all the attributes of the view were overwritten. This is contrary to the user's expectations. So some of the view attributes are preserved now : namely security and algorithm. This means that if they are not specified in ALTER VIEW their values are preserved from CREATE VIEW instead of being defaulted.
-
mikael/pappa@dator5.(none) authored
into dator5.(none):/home/pappa/bug18198
-
mikael/pappa@dator5.(none) authored
-
- 30 Jul, 2006 2 commits
-
-
sergefp@mysql.com authored
-
Fixing test result.
-
- 29 Jul, 2006 6 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
-
sergefp@newbox.mylan authored
into mysql.com:/home/psergey/mysql-5.1-bug14940-r4
-
sergefp@mysql.com authored
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.0-opt-mysql
-
evgen@sunlight.local authored
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
-
evgen@sunlight.local authored
into sunlight.local:/home/evgen/bk-trees/mysql-5.1-opt
-