- 09 Aug, 2003 1 commit
-
-
wax@mysql.com authored
replace HAVE_SETFILEPOINTER with __WIN__
-
- 30 Jul, 2003 5 commits
-
-
wax@mysql.com authored
into mysql.com:/home/wax/mysql/mysql-4.0chsize
-
wax@mysql.com authored
Add functions SetFilePointerEx and SetEndOfFile for huge tables instead of chsize Move chsize to right place
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-merged_qc-4.0
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-4.0-bugfix
-
bell@sanja.is.com.ua authored
-
- 29 Jul, 2003 2 commits
-
-
dlenev@mysql.com authored
ignorant about ssl_type attribute
-
heikki@hundin.mysql.fi authored
Fix bug introduced in 4.0.13 and reported by Emic: if a CREATE TABLE ended in a comment, a memory overrun could happen
-
- 28 Jul, 2003 2 commits
-
-
heikki@hundin.mysql.fi authored
innodb_fast_shutdown CAN take an argument though it was not specified so in mysqld.cc
-
guilhem@mysql.com authored
binary logging.
-
- 26 Jul, 2003 2 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
so that it really tests replication of SET FOREIGN_KEY_CHECKS (previously it used MyISAM).
-
- 25 Jul, 2003 3 commits
-
-
heikki@hundin.mysql.fi authored
Merge trx0trx.c: Print more info about a trx in SHOW INNODB status; try to find the bug reported by Plaxo buf0buf.c: Check that page log sequence numbers are not in the future log0recv.c, log0log.c: Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
-
gluh@gluh.mysql.r18.ru authored
into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.fix
-
gluh@gluh.mysql.r18.ru authored
-
- 24 Jul, 2003 4 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
just a flush_relay_log_info() at the end of CHANGE MASTER (there was already flush_master_info()).
-
guilhem@mysql.com authored
I extended the task to cleaning error messages, making them look nicer, and making the output of SHOW SLAVE STATUS (column Last_error) be as complete as what's printed on the .err file; previously we would have, for a failure of a replicated LOAD DATA INFILE: - in the .err, 2 lines: "duplicate entry 2708 for key 1" "failed loading SQL_LOAD-5-2-2.info" - and in SHOW SLAVE STATUS, only: "failed loading SQL_LOAD-5-2-2.info". Now SHOW SLAVE STATUS will contain the concatenation of the 2 messages.
-
miguel@hegel.local authored
-
- 23 Jul, 2003 1 commit
-
-
serg@serg.mylan authored
-
- 22 Jul, 2003 6 commits
-
-
gluh@gluh.mysql.r18.ru authored
into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.fix
-
gluh@gluh.mysql.r18.ru authored
-
gluh@gluh.mysql.r18.ru authored
Here is fix for bug 554. Added configure options --with-openssl-includes[=DIR] and --with-openssl-libs[=DIR]
-
lenz@mysql.com authored
- bumped up version number in configure.in to 4.0.15
-
heikki@hundin.mysql.fi authored
Fix bug: if there was a 'record too long' error in an insert, InnoDB forgot to free reserved file space extents; they were only freed in mysqld restart
-
heikki@hundin.mysql.fi authored
Fix an error in the previous push
-
- 21 Jul, 2003 3 commits
-
-
heikki@hundin.mysql.fi authored
Fix bug reported by Dyego Souza do Carmo: if a row becomes too long, > 8000 bytes, in an update, then InnoDB simply removes the clustered index record and does not report of table handler error 139
-
serg@serg.mylan authored
-
serg@serg.mylan authored
-
- 19 Jul, 2003 2 commits
-
-
hf@deer.(none) authored
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.0
-
- 18 Jul, 2003 7 commits
-
-
monty@mashka.(none) authored
into mashka.(none):/home/my/mysql-4.0
-
monty@mashka.(none) authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.0
-
monty@narttu.mysql.fi authored
-
monty@narttu.mysql.fi authored
Fixed memory overrun when doing REPAIR on table with multi-part auto_increment key where one part was a packed CHAR
-
- 17 Jul, 2003 1 commit
-
-
serg@serg.mylan authored
-
- 16 Jul, 2003 1 commit
-
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-