- 03 Aug, 2007 2 commits
-
-
msvensson@shellback.(none) authored
-
msvensson@shellback.(none) authored
-
- 27 Jul, 2007 2 commits
-
-
iggy@alf.(none) authored
into alf.(none):/src/bug30103/my50-bug30103
-
iggy@alf.(none) authored
- Add CMake rule to remove files.
-
- 25 Jul, 2007 2 commits
-
-
gbichot@production.mysql.com authored
internal ones (like those of GROUP BY): fixing the --help text.
-
iggy@amd64.(none) authored
- Sign executables with MySQL AB security certificate.
-
- 24 Jul, 2007 1 commit
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/jul24/50
-
- 20 Jul, 2007 7 commits
-
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp3/mysql-5.0-build
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/29898-bug-5.0-opt-mysql
-
joerg@trift-lap.none authored
into trift-lap.none:/MySQL/M50/push-5.0
-
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b28125/b28125.5.0
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
Result adjusted.
-
- 19 Jul, 2007 17 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0.46
-
df@pippilotta.erinye.com authored
-
evgen@moonbone.local authored
The Item_date_typecast::val_int function doesn't reset null_value flag. This makes all values that follows the first null value to be treated as nulls and led to a wrong result. Now the Item_date_typecast::val_int function correctly sets the null_value flag for both null and non-null values.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/29850-bug-5.0-opt-mysql
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/50
-
evgen@moonbone.local authored
a temporary table. The result string of the Item_func_group_concat wasn't initialized in the copying constructor of the Item_func_group_concat class. This led to a wrong charset of GROUP_CONCAT result when the select employs a temporary table. The copying constructor of the Item_func_group_concat class now correctly initializes the charset of the result string.
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29687/my50-29687
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29687/my50-29687
-
tsmith@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/tsmith-tmp/mysql-5.0-maint
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
joerg@trift-lap.none authored
by renaming "include/md5.h" to "include/my_md5.h". Fixes bug#14151.
-
i5 compatibility
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
- 18 Jul, 2007 6 commits
-
-
cmiller@zippy.cornsilk.net authored
when creating table Federated tables had an artificially low maximum of key length, because the handler failed to implement a method to return it and the default value is taked from the prototype handler. Now, implement that method and return the maximum possible key length, which is that of InnoDB.
-
gshchepa/uchum@gleb.loc authored
For each view the mysqldump utility creates a temporary table with the same name and the same columns as the view in order to satisfy views that depend on this view. After the creation of all tables, mysqldump drops all temporary tables and creates actual views. However, --skip-add-drop-table and --compact flags disable DROP TABLE statements for those temporary tables. Thus, it was impossible to create the views because of existence of the temporary tables with the same names.
-
kent@mysql.com/kent-amd64.(none) authored
Allow to set mysqld exe suffix
-
gkodinov/kgeorge@magare.gmz authored
table (datadir) Set errno when retunring an error in my_create_with_symlink.
-
Problem: we may break a multibyte char sequence using a key reduced to maximum allowed length for a storage engine (that leads to failed assertion in the innodb code, see also #17530). Fix: align truncated key length to multibyte char boundary.
-
sergefp@mysql.com authored
-
- 17 Jul, 2007 3 commits
-
-
sergefp@mysql.com authored
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-