- 21 Oct, 2004 1 commit
-
-
unknown authored
Fix bug #5961: release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users innobase/row/row0ins.c: Fix bug #5961: release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users innobase/row/row0mysql.c: Fix bug #5961: release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users
-
- 20 Oct, 2004 3 commits
-
-
unknown authored
mysql-test/r/innodb-lock.result: Fix test case (old one didn't test things correctly) mysql-test/t/innodb-lock.test: Fix test case (old one didn't test things correctly) mysys/thr_lock.c: More debugging information sql/mysqld.cc: Enable innodb_table_locks as default, as otherwise there is a possibility for deadlocks sql/sql_base.cc: More debug information
-
unknown authored
into mysql.com:/home/my/mysql-4.0 libmysql/libmysql.c: Auto merged
-
unknown authored
Rename innodb_table_locks_old_behavior -> innodb_table_locks Set innodb_table_locks to off by default to get same behaviour as in MySQL 4.0.20 (This means that Innodb ignore table locks by default, which makes it easier to combine MyISAM and InnoDB to simulate a transaction) libmysql/libmysql.c: Use ulong instead of unsigned long Reuse _dig_vec() myisam/myisampack.c: Simplify code mysql-test/r/innodb-lock.result: new test case mysql-test/t/innodb-lock.test: new test case sql/ha_innodb.cc: Rename innodb_table_locks_old_behavior -> innodb_table_locks sql/mysqld.cc: Rename innodb_table_locks_old_behavior -> innodb_table_locks Set this off by default to get same behaviour as in MySQL 4.0.20 sql/set_var.cc: Rename innodb_table_locks_old_behavior -> innodb_table_locks sql/sql_class.h: Rename innodb_table_locks_old_behavior -> innodb_table_locks
-
- 19 Oct, 2004 3 commits
- 17 Oct, 2004 2 commits
-
-
unknown authored
into goetia.(none):/home/dellis/mysqlab/bk/mysql-4.0 BitKeeper/etc/logging_ok: auto-union sql/mysqld.cc: Auto merged
-
unknown authored
BUG #5731 key_buffer_size not properly restricted to 4GB; use UINT_MAX32 for clarity. sql/mysqld.cc: BUG #5731 key_buffer_size not properly restricted to 4GB; use UINT_MAX32 for clarity.
-
- 16 Oct, 2004 2 commits
- 15 Oct, 2004 2 commits
- 14 Oct, 2004 2 commits
-
-
unknown authored
into mysql.com:/home/mydev/mysql-4.0-bug5625 sql/ha_myisam.cc: Auto merged sql/sql_table.cc: Auto merged
-
unknown authored
Added a try to a normal repair() if repair_by_sort() failed. This was not done with ENABLE KEYS and OPTIMIZE TABLE. Fixed error code handling in mysql_alter_table(). sql/ha_myisam.cc: BUG#5625 - MyISAM Index corruption on ALTER TABLE x ENABLE KEYS due to full tmpdir. Added a try to a normal repair() if repair_by_sort() failed. This was not done with ENABLE KEYS and OPTIMIZE TABLE. sql/sql_table.cc: BUG#5625 - MyISAM Index corruption on ALTER TABLE x ENABLE KEYS due to full tmpdir. Added a translation from 'bool' return value to '< 0' error indication, which is used within mysql_execute_command() and must as such be handed over by mysql_alter_table(). A returncode >= 0 is interpreted as 'I have already called send_ok()'.
-
- 13 Oct, 2004 1 commit
-
-
unknown authored
innodb_table_locks_old_behavior: do not acquire an InnoDB table lock for LOCK TABLES, as in mysql-4.0.18 and earlier. sql/ha_innodb.cc: Do not acquire an InnoDB table lock for LOCK TABLES if innodb_table_locks_old_behavior is enabled. sql/mysqld.cc: Added innodb_table_locks_old_behavior sql/set_var.cc: Added innodb_table_locks_old_behavior sql/sql_class.h: Added innodb_table_locks_old_behavior
-
- 12 Oct, 2004 2 commits
-
-
unknown authored
Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous value HA_ERR_CANNOT_ADD_FOREIGN, but misleading still; we should introduce to 5.0 a proper MySQL error code sql/ha_innodb.cc: Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous value HA_ERR_CANNOT_ADD_FOREIGN, but misleading still; we should introduce to 5.0 a proper MySQL error code
-
unknown authored
into hundin.mysql.fi:/home/heikki/mysql-4.0
-
- 11 Oct, 2004 3 commits
-
-
unknown authored
into mysql.com:/mnt/tmp/mysql-4.0-bug-myisampack
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
when one connection had done FLUSH TABLES WITH READ LOCK, some updates, and then COMMIT, it was accepted but my_error() was called and so, while client got no error, error was logged in binlog. We now don't call my_error() in this case; we assume the connection know what it does. This problem was specific to 4.0.21. The change is needed to make replication work with existing versions of innobackup. sql/lock.cc: If a connection has done FLUSH TABLES WITH READ LOCK and now is doing COMMIT, don't give error (applies only if it's the same connection; others' COMMITs are still blocked).
-
- 09 Oct, 2004 1 commit
-
-
unknown authored
Fix bug #5960: if one updated a column so that its size changed, or updated it to an externally stored (TEXT or BLOB) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row innobase/trx/trx0rec.c: Fix bug #5960: if one updated a column so that its size changed, or updated it to an externally stored (TEXT or BLOB) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row
-
- 08 Oct, 2004 1 commit
-
-
unknown authored
(Fixed this by backporting some logic from 4.1)
-
- 07 Oct, 2004 2 commits
-
-
unknown authored
BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
unknown authored
in the error monitor thread. (Bug #5898) innobase/include/sync0arr.h: sync_array_print_long_waits(): return error status innobase/srv/srv0srv.c: srv_error_monitor_thread(): Keep track on successive fatal timeouts, and crash the server only if the timeouts have been exceeded for several times in succession. innobase/sync/sync0arr.c: sync_array_print_long_waits(): return error status
-
- 06 Oct, 2004 3 commits
-
-
unknown authored
into build.mysql.com:/users/rburnett/mysql-4.0
-
unknown authored
myisam/mi_locking.c: More comments sql/mysql_priv.h: Change mode to uint (as it's a bitmap) sql/sql_handler.cc: Change mode to uint (as it's a bitmap) Fixed DBUG_PRINT to use same format as other MySQL code
-
unknown authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b5733 sql/records.cc: Auto merged
-
- 05 Oct, 2004 11 commits
-
-
unknown authored
into mysql.com:/home/my/mysql-4.0 sql/sql_table.cc: Auto merged
-
unknown authored
Cleaned up patch for checking locks for multi-table updates myisam/mi_close.c: Reverted patch for new usage of open_counts myisam/mi_locking.c: Reverted patch for new usage of open_counts sql/ha_myisam.cc: Reverted patch for new usage of open_counts sql/handler.cc: Removed compiler warning sql/sql_acl.cc: Removed compiler warning sql/sql_table.cc: No need to unlock after failed call to external_lock() sql/sql_update.cc: Cleaned up (and made it more secure) patch for checking locks for multi-table updates
-
unknown authored
into deer.(none):/home/hf/work/mysql-4.0
-
unknown authored
Recusive part leads to stack overflow sql/sql_cache.cc: Recursion removed from Query_cache::allocate_data_chain
-
unknown authored
into hundin.mysql.fi:/home/marko/k/mysql-4.0
-
unknown authored
into hundin.mysql.fi:/home/marko/k/mysql-4.0
-
unknown authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
-
unknown authored
sql/sql_union.cc: Fixing a non-critical bug in 4.0 UNION's which results in erronously calculated number o fexamined rows. This value is displayed in the slow query log. This is a bug number #5879.
-
unknown authored
into mysql.com:/home/mydev/mysql-4.0
-
unknown authored
-
unknown authored
into mysql.com:/home/mydev/mysql-4.0-bug4286 sql/sql_base.cc: Auto merged sql/sql_class.h: Auto merged sql/sql_table.cc: Auto merged
-
- 04 Oct, 2004 1 commit
-
-
unknown authored
Original code was checking ! unix_socket for local_file flag. This doesn't work and so was removed. Now to import a local file, you must use the --local command line option. mysqlimport.c: Removed check of unix_socket to set local_file client/mysqlimport.c: Removed check of unix_socket to set local_file
-