- 29 Jan, 2004 3 commits
-
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
monty@mysql.com authored
This fixed problem with index reads on character fields with BDB tables. (Bug #2509)
-
heikki@hundin.mysql.fi authored
Fix bug: InnoDB row count and index cardinality estimates wrapped over at 512 million in 32-bit computers
-
- 28 Jan, 2004 2 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
reset errors (in thd) before executing the event. Otherwise if an event is ignored because of replicate-*-table rules (error ER_SLAVE_IGNORED_TABLE) this error code may remain in thd->net and the next event may pick it.
-
- 27 Jan, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug #2483 with InnoDB, UNIQUE secondary index, and NULL values in that unique index; with the IS NULL predicate, InnoDB returned only the first matching row, though there can be many
-
- 22 Jan, 2004 5 commits
-
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2298
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2290/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2290/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
-
ram@gw.mysql.r18.ru authored
<monty> ramil, in MySQL/MyISAM we should only strip end space, not 'space-like' characters. <monty> This is according to SQL; When doing a comparision end space and only end space are ignored.
-
- 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 6 commits
-
-
vva@eagle.mysql.r18.ru authored
-
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 4 commits
-
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.0-root
-
konstantin@mysql.com authored
-
ram@gw.mysql.r18.ru 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.
-