- 25 Sep, 2006 2 commits
-
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-4.1.15428
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-4.1.15428
-
- 20 Sep, 2006 1 commit
-
-
igor@rurik.mysql.com authored
Any default value for a enum fields over UCS2 charsets was corrupted when we put it into the frm file, as it had been overwritten by its HEX representation. To fix it now we save a copy of structure that represents the enum type and when putting the default values we use this copy.
-
- 19 Sep, 2006 1 commit
-
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-4.1-opt
-
- 18 Sep, 2006 1 commit
-
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
- 16 Sep, 2006 1 commit
-
-
igor@rurik.mysql.com authored
statement that uses an aggregating IN subquery with HAVING clause. A wrong order of the call of split_sum_func2 for the HAVING clause of the subquery and the transformation for the subquery resulted in the creation of a andor structure that could not be restored at an execution of the prepared statement.
-
- 15 Sep, 2006 2 commits
-
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B21180-4.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
- 14 Sep, 2006 2 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/work/21677-bug-4.1-opt-mysql
-
evgen@moonbone.local authored
Added the test case for bug#21677: Wrong result when comparing a DATE and a DATETIME in BETWEEN
-
- 12 Sep, 2006 1 commit
-
-
evgen@moonbone.local authored
Removed changes to the Item_func_between::fix_length_and_dec() made in the fix for bug#16377 query_cache.result: Corrected a test case after removing a fix for bug#16377
-
- 08 Sep, 2006 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
VALUES() was considered a constant. This caused replacing (or pre-calculating) it using uninitialized values before the actual execution takes place. Mark it as a non-constant (still not dependent of tables) to prevent the pre-calculation.
-
- 07 Sep, 2006 1 commit
-
-
evgen@moonbone.local authored
Corrected test case after removal of fix for bug#16377 type_date.test: Corrected test case after removal of fix for bug#16377 item_cmpfunc.cc: Removed changes to the agg_cmp_type() made in the for bug#16377
-
- 06 Sep, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
-
- 05 Sep, 2006 3 commits
-
-
gkodinov/kgeorge@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/B16792-4.1-opt
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
gkodinov/kgeorge@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/B21392-4.1-opt
-
- 04 Sep, 2006 5 commits
-
-
gkodinov/kgeorge@macbook.gmz authored
1003: Incorrect table name in multi-table DELETE the set of tables to delete from actually references then tables in the other list, e.g: DELETE alias_of_t1 FROM t1 alias_of_t1 WHERE .... is a valid statement. So we must turn off table name syntactical validity check for alias_of_t1 because it's not a table name (even if it looks like one). In order to do that we add a special flag (TL_OPTION_ALIAS) to disable the name checking for the aliases in multi-table DELETE.
-
holyfoot/hf@mysql.com/deer.(none) authored
The problem is that on some Mac OS X-es the file writing/reading call with zero bytes to read/write returns error. So here i try to eliminate that kinds of calls.
-
timour/timka@lamia.home authored
Fix an error in the bug fix.
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
jonas@perch.ndb.mysql.com authored
fix deadlock if master switches log file in parallell with "show master logs"
-
- 01 Sep, 2006 7 commits
-
-
timour/timka@lamia.home authored
into lamia.home:/home/timka/mysql/src/4.1-bug-21787
-
timour/timka@lamia.home authored
The problem was due to a prior fix for BUG 9676, which limited the rows stored in a temporary table to the LIMIT clause. This optimization is not applicable to non-group queries with aggregate functions. The fix disables the optimization in this case.
-
msvensson@neptunus.(none) authored
- Dont test "encrypt" in ctype_ucs
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
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
-