Re: MySQL/InnoDB-4.1.9 is released

Nick, - Original Message - From: "Nick Arnett" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Friday, January 14, 2005 9:28 PM Subject: Re: MySQL/InnoDB-4.1.9 is released Heikki Tuuri wrote: http://dev.mysql.com/doc/mysql/en/LOCK_TABLES.html " The co

Re: MySQL/InnoDB-4.1.9 is released

Heikki Tuuri wrote: http://dev.mysql.com/doc/mysql/en/LOCK_TABLES.html " The correct way to use LOCK TABLES with transactional tables, like InnoDB, is to set AUTOCOMMIT = 0 and not to call UNLOCK TABLES until you commit the transaction explicitly. When you call LOCK TABLES, InnoDB internally tak

Re: MySQL/InnoDB-4.1.9 is released

Nick, - Original Message - From: "Nick Arnett" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Friday, January 14, 2005 7:39 PM Subject: Re: MySQL/InnoDB-4.1.9 is released Heikki Tuuri wrote: * Do not acquire an internal InnoDB table lock in LOCK TABLES

Re: MySQL/InnoDB-4.1.9 is released

Heikki Tuuri wrote: * Do not acquire an internal InnoDB table lock in LOCK TABLES if AUTOCOMMIT=1. This helps in porting old MyISAM applications to InnoDB. InnoDB table locks in that case caused very easily deadlocks. Could you explain a bit more about how this relates to MyISAM? Is it just tha

MySQL/InnoDB-4.1.9 is released

Hi! InnoDB is the MySQL table type that supports FOREIGN KEY constraints, row-level locking, Oracle-style consistent, non-locking SELECTs, multiple tablespaces, and a non-free online hot backup tool. Release 4.1.9 is mainly a bugfix release. This release fixes the CRITICAL BUG #7496 in the inno