- 21 Jan, 2004 7 commits
-
-
serg@serg.mylan authored
-
serg@serg.mylan authored
-
serg@serg.mylan authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-
lenz@mysql.com authored
spec file after the build as RPM has its own option for this
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-
- 20 Jan, 2004 5 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
do not write the Execute_load_log_event if there was no Create_file_log_event (empty file).
-
lenz@mysql.com authored
manpage) turned out as a major overhaul of all man pages: - renamed all *.1 files to *.1.in to act as templates which are being processed at build time - replaced some hard-coded values with place holder that are being replaced with the proper values at build time - Updated list of available man pages in the SEE ALSO section and added a hint to the manual for more details - Added a BUGS section to all pages, referring to the bugs DB - Updated some obsolete URLs and mail addresses The actual content of these man pages should probably be cross-checked for correctness, though...
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
- 19 Jan, 2004 3 commits
-
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
monty@mysql.com authored
-
- 18 Jan, 2004 1 commit
-
-
guilhem@mysql.com authored
I remove the --old-rpl-compat which produces broken binlogs readable neither by 4.0 nor by 3.23. This option is a leftover of the early replication of 4.0.0, when it was still partly compatible with 3.23. I explained this to the user in the bug report.
-
- 16 Jan, 2004 3 commits
-
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.0-root
-
konstantin@mysql.com authored
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
-
- 15 Jan, 2004 7 commits
-
-
monty@mysql.com authored
-
greg@mysql.com authored
for re-working project files and enabling remote builds.
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
lenz@mysql.com authored
started via mysqld_safe (BUG#2114) Thanks to Rodrigo Marchant for the suggestion
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-
- 14 Jan, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug: FOREIGN KEY ... ON UPDATE/DELETE NO ACTION must check the foreign key constraint, not ignore it. Peter Gulutzan said that NO ACTION should check the constraint as deferred, at the end of the SQL statement, while RESTRICT should check it immediately. Since we do not have defered constraints in InnoDB, this bug fix makes InnoDB to check NO ACTION constraints immediately, like it checks RESTRICT constraints.
-
- 13 Jan, 2004 6 commits
-
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-
lenz@mysql.com authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
lenz@mysql.com authored
for the MySQL root user (BUG#2375)
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
- 12 Jan, 2004 3 commits
-
-
greg@mysql.com authored
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
-
Sinisa@sinisa.nasamreza.org authored
A fix for a bug #3189, pertaining to crashing MySQL server when a query with MIN / MAX on the BLOB column is to be optimised
-
- 11 Jan, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
The test might fail if one runs it at 23:59:59 Dec 31
-
- 09 Jan, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2231
-
- 08 Jan, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
INDEX+LIKE, don't take the ESCAPE character. (ver. 2)
-
- 07 Jan, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Start InnoDB Monitor if 80 % of the buffer pool occupied by adaptive has or lock heaps; do not print the same warning more than 1 time
-