mariadb/trx
marko a9a21fb983 branches/zip: Do not release the data dictionary latch while holding locks
to the data dictionary records.  This should fix Issue #83.

row_drop_table_for_mysql_no_commit(): Rename back to
row_drop_table_for_mysql().  Commit the transaction if the data
dictionary was not locked when the function was called.  Otherwise,
neither commit the transaction nor unlock the data dictionary.

row_merge_drop_table(): Let row_drop_table_for_mysql() take care of
locking the data dictionary.

dict_create_or_check_foreign_constraint_tables(),
trx_rollback_active(), row_create_table_for_mysql(),
row_create_index_for_mysql(), row_table_add_foreign_constraints():
Explicitly commit the transaction, because row_drop_table_for_mysql()
would no longer commit it, given that the data dictionary will be
locked during the calls.

Approved by Sunny (over IM). rb://23
2008-10-08 08:54:16 +00:00
..
trx0i_s.c branches/zip: 2008-08-07 10:59:49 +00:00
trx0purge.c branches/zip: Introduce UNIV_INTERN, a linkage specifier for InnoDB-global 2008-02-06 14:17:36 +00:00
trx0rec.c branches/zip: Non-functional change: 2008-09-22 06:59:58 +00:00
trx0roll.c branches/zip: Do not release the data dictionary latch while holding locks 2008-10-08 08:54:16 +00:00
trx0rseg.c branches/zip: Non-functional change: 2008-09-22 06:59:58 +00:00
trx0sys.c branches/zip: Non-functional change: 2008-09-22 06:59:58 +00:00
trx0trx.c branches/zip: When creating an index in innodb_strict_mode, check that 2008-09-18 12:31:17 +00:00
trx0undo.c branches/zip: Non-functional change: 2008-09-22 06:59:58 +00:00