- 22 Apr, 2003 1 commit
-
-
monty@narttu.mysql.fi authored
Backported fix from 4.1 for bug 212: SELECT query containing a NATURAL JOIN and parentheses in the WHERE clause
-
- 07 Apr, 2003 2 commits
-
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-3.23
-
monty@mashka.mysql.fi authored
Fixed problem with not freed thr_alarm() on slave connect
-
- 04 Apr, 2003 1 commit
-
-
vva@eagle.mysql.r18.ru authored
-
- 03 Apr, 2003 2 commits
-
-
monty@narttu.mysql.fi authored
-
monty@narttu.mysql.fi authored
-
- 01 Apr, 2003 1 commit
-
-
guilhem@mysql.com authored
logged, but read as LOAD DATA INFILE REPLACE" This was just bad && instead of &, but nasty consequences. This should be merged to 4.0 BUT it will not be automatic (some code has moved from log_event.h to log_event.cc, and log_event.cc has changed); please Merging Man, do 'bk grep REPLACE_FLAG' in 4.0/sql to find all the new places.
-
- 25 Mar, 2003 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
least one BLOB column.
-
- 24 Mar, 2003 2 commits
-
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-3.23
-
monty@narttu.mysql.fi authored
-
- 19 Mar, 2003 2 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-3.23
-
guilhem@mysql.com authored
only do it if the user specifies --delete-master-logs (new option). Safer + fixes bug #159.
-
- 18 Mar, 2003 1 commit
-
-
monty@narttu.mysql.fi authored
-
- 16 Mar, 2003 2 commits
-
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-3.23
-
heikki@hundin.mysql.fi authored
Test if merging from 3.23 to 4.0 succeeds
-
- 15 Mar, 2003 2 commits
-
-
heikki@hundin.mysql.fi authored
Fix bug number 154: GROUP BY and DISTINCT could treat NULL values inequal
-
lenz@mysql.com authored
- bumped up version number to 3.23.57 in configure.in
-
- 14 Mar, 2003 3 commits
-
-
monty@mashka.mysql.fi authored
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-3.23
-
monty@mashka.mysql.fi authored
-
- 13 Mar, 2003 4 commits
-
-
heikki@hundin.mysql.fi authored
Fix bug: MySQL could erroneously return Empty set if InnoDB estimated index range size to 0 records though the range was not empty; MySQL also failed to do the next-key locking in the case of an empty index range
-
serg@serg.mysql.com authored
-
monty@mashka.mysql.fi authored
-
serg@serg.mysql.com authored
into serg.mysql.com:/usr/home/serg/Abk/mysql
-
- 12 Mar, 2003 6 commits
-
-
bell@sanja.is.com.ua authored
-
serg@serg.mysql.com authored
typo fixed
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql
-
Sinisa@sinisa.nasamreza.org authored
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-3.23
-
monty@mashka.mysql.fi authored
Changed that analyse(#) also affects strings
-
- 11 Mar, 2003 10 commits
-
-
lenz@mysql.com authored
for the patch) (bug #135)
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/work-rand-3.23
-
serg@serg.mysql.com authored
into serg.mysql.com:/usr/home/serg/Abk/mysql
-
serg@serg.mysql.com authored
-
monty@mashka.mysql.fi authored
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql
-
lenz@mysql.com authored
-
bell@sanja.is.com.ua authored
-
lenz@mysql.com authored
(it barfs on these with a syntax error)
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql
-