An error occurred fetching the project authors.
- 03 Oct, 2006 3 commits
-
-
msvensson@shellback.(none) authored
- Change con_host to ds_connection_name.str
-
msvensson@shellback.(none) authored
-
msvensson@shellback.(none) authored
- ie. backport from 5.1 - also update testcase error dected by new version
-
- 01 Sep, 2006 3 commits
-
-
msvensson@shellback.(none) authored
into shellback.(none):/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@shellback.(none) authored
-
jimw@rama.(none) authored
into rama.(none):/home/jimw/my/mysql-4.1-21288
-
- 31 Aug, 2006 3 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint
-
cmiller@zippy.cornsilk.net authored
single file is a bad practice.
-
- 30 Aug, 2006 8 commits
-
-
tsmith@maint2.mysql.com authored
into maint2.mysql.com:/data/localhome/tsmith/bk/41
-
tsmith@maint2.mysql.com authored
into maint2.mysql.com:/data/localhome/tsmith/bk/41
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug04053/my41-bug04053
-
cmiller@zippy.cornsilk.net authored
event' from master" Since there is no repeatable test case, and this is obviously wrong, this is the most conservative change that might possibly work. The syscall read() wasn't checked for a negative return value for an interrupted read. The kernel sys_read() returns -EINTR, and the "library" layer maps that to return value of -1 and sets errno to EINTR. It's impossible (on Linux) for read() to set errno EINTR without the return value being -1 . So, if we're checking for EINTR behavior, we should not require that the return value be zero.
-
tsmith@maint2.mysql.com authored
-
tsmith@maint2.mysql.com authored
-
tsmith@maint2.mysql.com authored
into maint2.mysql.com:/data/localhome/tsmith/bk/bfx/41
-
gluh@mysql.com/gluh.(none) authored
Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte
-
- 29 Aug, 2006 1 commit
-
-
tsmith@maint2.mysql.com authored
into maint2.mysql.com:/data/localhome/tsmith/bk/41
-
- 28 Aug, 2006 2 commits
-
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/bugfixin/41
-
tsmith@maint1.mysql.com authored
-
- 27 Aug, 2006 1 commit
-
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
- 26 Aug, 2006 2 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
msvensson@neptunus.(none) authored
-
- 25 Aug, 2006 6 commits
-
-
msvensson@neptunus.(none) authored
Null merge to 5.0
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
Default is "var/tmp"
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@neptunus.(none) authored
-
- 24 Aug, 2006 6 commits
-
-
sergefp@mysql.com authored
-
sergefp@mysql.com authored
Must not use Item_direct_ref in HAVING because it points to the new value (witch is not yet calculated for the first row).
-
into mysql.com:/Users/kent/mysql/bk/mysql-4.1-maint
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/41
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/41
-
tsmith/tim@siva.hindu.god authored
- Fix typo in Item_func_export_set::fix_length_and_dec() which caused character set aggregation to fail - Remove default argument from last arg of agg_arg_charsets() function, to reduce potential errors
-
- 23 Aug, 2006 5 commits
-
-
tsmith/tim@siva.hindu.god authored
into siva.hindu.god:/usr/home/tim/m/bk/41
-
tsmith/tim@siva.hindu.god authored
Remove some sql_print_error() calls which were triggered by user error (i.e., not server-level events at all). Also, convert an sql_print_error -> sql_print_information for a non-error server event.
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/41
-
timour/timka@lamia.home authored
into lamia.home:/home/timka/mysql/src/4.1-bug-21456
-
timour/timka@lamia.home authored
GROUP BY/DISTINCT pruning optimization must be done before ORDER BY optimization because ORDER BY may be removed when GROUP BY/DISTINCT sorts as a side effect, e.g. in SELECT DISTINCT <non-key-col>,<pk> FROM t1 ORDER BY <non-key-col> DISTINCT must be removed before ORDER BY as if done the other way around it will remove both.
-