An error occurred fetching the project authors.
- 14 Feb, 2005 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
Can't repeat information_schema test failure Fix for lowercase_table3 only
-
- 08 Feb, 2005 3 commits
-
-
hf@deer.(none) authored
-
marko@hundin.mysql.fi authored
Row_format=Redundant
-
jan@hundin.mysql.fi authored
single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog is used and isolation level of the transaction is not serializable. InnoDB uses consistent read in these cases for a selected table. Backported from 5.0.x.
-
- 07 Feb, 2005 1 commit
-
-
jan@hundin.mysql.fi authored
single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog is used and isolation level of the transaction is not serializable. InnoDB uses consistent read in these cases for a selected table.
-
- 03 Feb, 2005 1 commit
-
-
jan@hundin.mysql.fi authored
-
- 01 Feb, 2005 1 commit
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Support for COMMIT/ROLLBACK optional arguments
-
- 31 Jan, 2005 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 28 Jan, 2005 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 27 Jan, 2005 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 13 Jan, 2005 4 commits
-
-
heikki@hundin.mysql.fi authored
"Add a comment why data modifying SQL statements MUST always use a locking read in tables that they read: otherwise the execution is not serializable, and in many cases is not well-defined; we also merged the associated bug fix from 4.1"
-
heikki@hundin.mysql.fi authored
Merge from 4.0: Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
-
heikki@hundin.mysql.fi authored
Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
-
konstantin@mysql.com authored
-
- 12 Jan, 2005 2 commits
-
-
heikki@hundin.mysql.fi authored
Add comments about why the InnoDB latching order is obeyed also for the MySQL query cache mutex; add an error printf if that is not the case sync0sync.h: Assign sync0sync.h ranks also for the MySQL query cache mutex and the MySQL binlog mutex; the latching order must be obeyed also for these row0ins.c: Add a comment why the query cache invalidate operation cannot deadlock in a cascaded FOREIGN KEY operation
-
marko@hundin.mysql.fi authored
open interface for setting the "delete-on-close" flag.
-
- 11 Jan, 2005 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 08 Jan, 2005 1 commit
-
-
vtkachenko@intelp4d.mysql.com authored
- Create innodb_thread_concurrency as dynamic variable - Add innodb_thread_sleep_delay variable - Add innodb_free_tickets_to_enter variable
-
- 07 Jan, 2005 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 06 Jan, 2005 1 commit
-
-
monty@mysql.com authored
Split TABLE to TABLE and TABLE_SHARE (TABLE_SHARE is still allocated as part of table, will be fixed soon) Created Field::make_field() and made Field_num::make_field() to call this Added 'TABLE_SHARE->db' that points to database name; Changed all usage of table_cache_key as database name to use this instead Changed field->table_name to point to pointer to alias. This allows us to change alias for a table by just updating one pointer. Renamed TABLE_SHARE->real_name to table_name Renamed TABLE->table_name to alias Renamed TABLE_LIST->real_name to table_name
-
- 27 Dec, 2004 3 commits
-
-
heikki@hundin.mysql.fi authored
Return a sensible error code from DISCARD TABLESPACE, if it fails because the table is referenced by a FOREIGN KEY
-
heikki@hundin.mysql.fi authored
Correct typo
-
heikki@hundin.mysql.fi authored
Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
-
- 24 Dec, 2004 2 commits
-
-
vtkachenko@intelp4d.mysql.com authored
tabs replaced ha_innodb.cc: Comments removed
-
vtkachenko@intelp4d.mysql.com authored
Logging to logging@openlogging.org accepted sql_yacc.yy, sql_parse.cc, sql_lex.h, lex.h: Implements the SHOW MUTEX STATUS command set_var.cc, mysqld.cc, mysql_priv.h: Added new GLOBAL variable timed_mutexes ha_innodb.h: New function innodb_mutex_show_status ha_innodb.cc: Added new innodb variables in SHOW STATUS Implements the SHOW MUTEX STATUS command innodb.test, innodb.result: Added new row_lock_waits status variables tests. variables.test, variables.result: test new variable timed_mutexes ut0ut.c: New function ut_usectime. sync0sync.c: Mutex counting. sync0rw.c: New mutex parameters initialization. srv0srv.c: Counting row lock waits row0sel.c, row0mysql.c: Setting row_lock or table_lock state to thd. que0que.c: Added default no_lock_state to thd. univ.i: Added UNIV_SRV_PRINT_LATCH_WAITS debug define sync0sync.ic: Count mutex using. sync0sync.h: Added new parameters to mutex structure for counting. sync0rw.h: Added new parameters to rw_create_func. srv0srv.h: Added new innodb varuables to SHOW STATUS. que0que.h: Added thread lock states.
-
- 23 Dec, 2004 1 commit
-
-
sergefp@mysql.com authored
will call handler::position() during key scan. Undo the previous, less efficient fix (cset 2004-11-30 19:56:25+02:00, heikki@hundin.mysql.fi)
-
- 22 Dec, 2004 2 commits
-
-
heikki@hundin.mysql.fi authored
Add a comment that no InnoDB table lock is now acquired in LOCK TABLES if AUTOCOMMIT=1. This helps to avoid deadlocks when porting old MyISAM applications to InnoDB.
-
heikki@hundin.mysql.fi authored
If AUTOCOMMIT=1, do not acquire an InnoDB table lock in LOCK TABLES; this makes porting of old MyISAM applications to InnoDB easier, since in that mode InnoDB table locks caused deadlocks very easily
-
- 21 Dec, 2004 1 commit
-
-
jan@hundin.mysql.fi authored
-
- 17 Dec, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
that affected the UCS2 character set. (Bug #7350)
-
- 16 Dec, 2004 1 commit
-
-
jan@hundin.mysql.fi authored
-
- 14 Dec, 2004 1 commit
-
-
kaa@polly.local authored
-
- 13 Dec, 2004 2 commits
-
-
jan@hundin.mysql.fi authored
-
jan@hundin.mysql.fi authored
-
- 10 Dec, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
-
- 09 Dec, 2004 1 commit
-
-
jan@hundin.mysql.fi authored
transactional table locks to tables mentioned in the query. These locks are released at the end of the transaction automatically. This is fix for bugs #5655, #5998 and issue #3762.
-
- 07 Dec, 2004 1 commit
-
-
monty@mysql.com authored
Fixed compiler warnings String results in CREATE ... SELECT are now created as CHAR(0), VARCHAR(X) or TEXT() depending on item->max_length
-
- 06 Dec, 2004 1 commit
-
-
monty@mysql.com authored
Renamed HA_VAR_LENGTH to HA_VAR_LENGTH_PART Renamed in all files FIELD_TYPE_STRING and FIELD_TYPE_VAR_STRING to MYSQL_TYPE_STRING and MYSQL_TYPE_VAR_STRING to make it easy to catch all possible errors Added support for VARCHAR KEYS to heap Removed support for ISAM Now only long VARCHAR columns are changed to TEXT on demand (not CHAR) Internal temporary files can now use fixed length tables if the used VARCHAR columns are short
-
- 03 Dec, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 02 Dec, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
Implement more compact InnoDB record format. Old format is available as CREATE TABLE ... ROW_FORMAT=DYNAMIC.
-