- 19 May, 2005 4 commits
-
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/mysql-4.1
-
ramil@mysql.com authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
serg@serg.mylan authored
-
- 18 May, 2005 20 commits
-
-
serg@serg.mylan authored
-
bell@book.sanja.is.com.ua authored
into book.sanja.is.com.ua:/Users/bell/mysql/bk/work-4.1
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
when reporting an error, use an appropriate buffer for udf->name
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-4.1-4100
-
ingo@mysql.com authored
After review version. Added a condition for MERGE tables. These do not have unique indexes. But every key could be a unique key on the underlying MyISAM table. So get the maximum key length for MERGE tables instead of the maximum unique key length. This is used for buffer allocation in write_record().
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
-
jimw@mysql.com authored
-
jimw@mysql.com authored
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my41
-
pekka@mysql.com authored
-
bell@book.sanja.is.com.ua authored
into book.sanja.is.com.ua:/Users/bell/mysql/bk/work-4.1
-
bell@book.sanja.is.com.ua authored
-
igor@rurik.mysql.com authored
Added test cases for bug #7914. sql_select.cc: Fixed bug #7914: rollup over expresssions such as sum(a)+1.
-
igor@rurik.mysql.com authored
Added missing ';'.
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
serg@serg.mylan authored
-
tulin@dl145c.mysql.com authored
updated error message for ndb
-
matt@mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-4.1-build
-
- 17 May, 2005 1 commit
-
-
bell@book.sanja.is.com.ua authored
into book.sanja.is.com.ua:/Users/bell/mysql/bk/work-4.1
-
- 16 May, 2005 6 commits
-
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-4.1-bug10095
-
monty@mysql.com authored
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-4.1-bug10221
-
sergefp@mysql.com authored
-
bell@book.sanja.is.com.ua authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1
-
- 15 May, 2005 7 commits
-
-
kent@mysql.com authored
To solve bug#8455, call mysql_affected_rows() earlier, before query to find warnings
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-4.0-bug10095
-
sergefp@mysql.com authored
The problem: base_list::remove didn't modify base_list::last when removing the last list element. The fix: If we remove the last element, find the element before it (by walking from the beginning of the list) and set base_list::last accordingly. The list gets corrupted in both 4.0 and 4.1. There are no visible problems in current 4.1 because current 4.1 doesn't call where_cond->fix_fields() after constant propagation step.
-
kent@mysql.com authored
To solve bug#6193, also reset require when using 'eval' for running query mysql-test-run.pl: In cleanup, remove possible soft link to var directory
-
kent@mysql.com authored
Added option --vardir=<directory> for feature bug#10096
-
kent@mysql.com authored
Not to conflict with Windows return code 2 for "not found", use 62 for "skip" init_db.sql: Initial db updates
-
kent@mysql.com authored
Not to conflict with Windows return code 2 for "not found", use 62 for "skip" mysql-test-run.sh, suppress.purify: Use Purify suppress file
-
- 14 May, 2005 2 commits
-
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/cw/mysql-4.1
-
monty@mysql.com authored
-