unknown 238b226f26 Added innodb_locks_unsafe_for_binlog option. This option turns off Innodb ... next-key locking. Using this option the locks InnoDB sets on index records do not affect the ``gap'' before that index record. Thus, this option allows phantom problem. innobase/include/srv0srv.h: Added srv_locks_unsafe_for_binlog for innodb_locks_unsafe_for_binlog option. innobase/row/row0sel.c: If innodb_locks_unsafe_for_binlog option is used, we lock only the record, i.e. next-key locking is not used. Therefore, setting lock to the index record do not affect the ``gap'' before that index record. Thus, this option allows phantom problem, because concurrent insert operations are allowed inside the select range. innobase/srv/srv0srv.c: Added srv_locks_unsafe_for_binlog for innodb_locks_unsafe_for_binlog option. sql/ha_innodb.cc: Added innobase_locks_unsafe_for_binlog and srv_locks_unsafe_for_binlog for innodb_locks_unsafe_for_binlog option. sql/ha_innodb.h: Added innobase_locks_unsafe_for_binlog for innodb_locks_unsafe_for_binlog option. sql/mysqld.cc: Added OPT_INNODB_LOCKS_UNSAFE_FOR_BINLOG, innobase_locks_unsafe_for_binlog for innodb_locks_unsafe_for_binlog option. sql/set_var.cc: Added innodb_locks_unsafe_for_binlog and innobase_locks_unsafe_for_binlog for innodb_locks_unsafe_for_binlog option. BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted		2004-07-20 14:15:38 +03:00
..
config	Ensure that we use unix file format (no \r\n) for all new files	2004-03-20 12:48:14 +02:00
gone	- really deleted makefile.w32 to resolve a namespace conflict on	2003-02-03 14:39:15 +01:00
logging_ok	Added innodb_locks_unsafe_for_binlog option. This option turns off Innodb	2004-07-20 14:15:38 +03:00
notify	notify BitKeeper file /home/bk/mysql/BitKeeper/etc/notify	2000-08-02 01:45:37 +02:00
skipkeys	BK automatic LOD removal.	2002-11-07 11:20:17 +04:00