- 24 Jul, 2003 4 commits
-
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
just a flush_relay_log_info() at the end of CHANGE MASTER (there was already flush_master_info()). sql/sql_repl.cc: Comments. Flush relay-log.info after CHANGE MASTER, or the changes to the relay log parameters (relay log name and position, and the corresponding master's binlog name and position) will be lost if the slave mysqld is shutdown immediately after the CHANGE MASTER (without the slave threads being started).
-
unknown 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. sql/log_event.cc: Print the default database when replication stops because of an error. Previously, we had: "error "Duplicate entry 87987 for key 1", query 'insert into t values(87987)'", ie the db was not mentioned, making it hard for cases where the same table name is used in several databases. Lengthened some error messages (for failing replication of LOAD DATA: mention the table and the db). Changes so that SHOW SLAVE STATUS reports as complete errors as the .err file. sql/slave.cc: Removed a useless declaration (the rewrite_db() function is already declared in slave.h). Added missing ')' in error messages. Tried to make error messages look nicer (previously we had "do START SLAVE;, error_code=1062" now we'll have "do START SLAVE; . Error_code=1062". This form has been discussed, I agree it's no panacea, but it's still more readable like this. To be improved in the future :) sql/slave.h: declarations.
-
unknown authored
-
- 23 Jul, 2003 1 commit
-
-
unknown authored
-
- 22 Jul, 2003 6 commits
-
-
unknown authored
into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.fix
-
unknown authored
-
unknown authored
Here is fix for bug 554. Added configure options --with-openssl-includes[=DIR] and --with-openssl-libs[=DIR] acinclude.m4: Bug #554: Support for --with-openssl[=DIR]
-
unknown authored
- bumped up version number in configure.in to 4.0.15
-
unknown 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 innobase/btr/btr0cur.c: 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
-
unknown authored
Fix an error in the previous push innobase/btr/btr0cur.c: Fix an error in the previous push
-
- 21 Jul, 2003 3 commits
-
-
unknown 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 innobase/btr/btr0cur.c: 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
-
unknown authored
-
unknown authored
-
- 19 Jul, 2003 2 commits
-
-
unknown authored
myisam/mi_locking.c: Here we use F_EXTRA_LCK myisam/myisamchk.c: lines of "locking - emulation" replaced with mi_lock_database call myisam/myisamdef.h: no need for MI_TEMPORARY_TABLE sql/ha_myisam.cc: We use F_WRLCK instead MI_TEMPORARY_TABLE
-
unknown authored
into deer.(none):/home/hf/work/mysql-4.0
-
- 18 Jul, 2003 7 commits
-
-
unknown authored
into mashka.(none):/home/my/mysql-4.0
-
unknown authored
acinclude.m4: Fixed problem with openssl on RedHat 9 vio/viosocket.c: Removed compiler warning BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
unknown authored
into mysql.com:/space/my/mysql-4.0
-
unknown authored
into narttu.mysql.fi:/my/mysql-4.0
-
unknown authored
-
unknown authored
Fixed memory overrun when doing REPAIR on table with multi-part auto_increment key where one part was a packed CHAR myisam/mi_check.c: Fixed memory overrun in _mi_put_key_in_record myisam/mi_key.c: Fixed unnecessary memory allocation mysql-test/r/insert_select.result: Added test case for memory corruption mysql-test/t/insert_select.test: Added test case for memory corruption mysys/safemalloc.c: Removed compiler warnings sql/sql_acl.cc: Fixed core dump when running with --debug
-
- 17 Jul, 2003 1 commit
-
-
unknown authored
mysql-test/r/ctype_latin1_de.result: testing overlapping combos mysql-test/t/ctype_latin1_de.test: testing overlapping combos
-
- 16 Jul, 2003 5 commits
-
-
unknown authored
into mysql.com:/space/my/mysql-4.0-build
-
unknown authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_683/mysql-4.0
-
unknown authored
-
unknown authored
as requested by PeterZ support-files/my-innodb-heavy-4G.cnf.sh: - heavily reworked the comments and layout as requested by PeterZ
-
unknown authored
a node name was changed in manual.texi which resulted in a very large ReadMe.txt file, as the generating script could not find the (renamed) ending node. Fixed the ending node name in Docs/Makefile.am and the Docs/Support/generate-text-files.pl Perl script to make sure this does not happen again (I only discovered this because the Do-pkg script was not able to add the ReadMe.txt to the Apple Disk image because it ran out of disk space due to the size of the file) Docs/Makefile.am: - Fixed a node name that was changed in manual.texi and resulted in the generation of a _very_ large ReadMe.txt file (down to the very end of the manual, since the ending node was not found) Docs/Support/generate-text-files.pl: - added a safeguard: if the ending node was not found, abort with an error to indicate that the generated text file might be too large (as it would contain the whole manual, down from the starting node) - made some cosmetical changes
-
- 15 Jul, 2003 4 commits
-
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0 sql/handler.cc: Auto merged
-
unknown authored
myisammrg/myrg_open.c: never mark merge table as readonly even if all underlying myisam tables are readonly, otherwise ALTER TABLE merge UNION=(t1,t2,t3,...) will not work sql/handler.cc: map EACCES to ER_OPEN_AS_READONLY. can only happen on modifying merge table that has (some) read-only myisam tables
-
unknown authored
in mysqld_safe (commented out by default), to not override any options defined in my.cnf (thanks to Axel Schwenke from Jobpilot.de for the suggestion)
-
unknown authored
acinclude.m4: Made test for compress more reliable (for Solaris) sql/item_strfunc.cc: Portability fix (for Linux Alpha)
-
- 14 Jul, 2003 7 commits
-
-
unknown authored
mysql-test/r/rpl_max_relay_size.result: Auto merged
-
unknown authored
Fixed test for binary build mysql-test/r/rpl_max_relay_size.result: Fixed test for binary build mysql-test/t/rpl_max_relay_size.test: Fixed test for binary build sql/log.cc: Fixed wrong test in close
-
unknown authored
mysql-test/r/rpl_max_relay_size.result: result update mysql-test/t/rpl_max_relay_size.test: port-independent test
-
unknown authored
Correct a misleading error message about max row length sql/share/english/errmsg.txt: Correct a misleading error message about max row length
-
unknown authored
Revert the previous patch: MySQL would not allow creation of VARCHAR columns whose total max length is > 8000 bytes, though InnoDB can easily store them as trailing spaces are removed sql/ha_innodb.h: Revert the previous patch: MySQL would not allow creation of VARCHAR columns whose total max length is > 8000 bytes, though InnoDB can easily store them as trailing spaces are removed
-
unknown authored
Fix wrong error message: If one tried to create table with a very big row len, MySQL claimed the max len is 64 kB for InnoDB, while it normally is 8000 bytes sql/ha_innodb.h: Fix wrong error message: If one tried to create table with a very big row len, MySQL claimed the max len is 64 kB for InnoDB, while it normally is 8000 bytes
-
unknown authored
mysql-test/t/rpl_flush_log_loop.test: Add timer to avoid problem when 'flush logs' is executed before we have read all data from master sql/log.cc: Better fix for bug #791: Mark log as LOG_TO_BE_OPENED instead of LOG_CLOSED when it's closed and opened. sql/mysqld.cc: Better startup message sql/slave.cc: Fix argument to close() sql/sql_class.h: Better handling of log.close()
-