The following issue has been RESOLVED. ====================================================================== http://www.dbmail.org/mantis/view.php?id=296 ====================================================================== Reported By: MagnusSundberg Assigned To: aaron ====================================================================== Project: DBMail Issue ID: 296 Category: installation scripts Reproducibility: always Severity: minor Priority: normal Status: resolved Resolution: fixed Fixed in Version: SVN Trunk ====================================================================== Date Submitted: 31-Jan-06 12:02 CET Last Modified: 29-Apr-06 04:09 CEST ====================================================================== Summary: MySQL add_header_tables.mysql Description: Just a small note on the programming of this file. My beleif is that when you issue CREATE TABLE MySQL automatically commits. Yhe file https://svn.ic-s.nl/svn/dbmail/trunk/dbmail/sql/mysql/add_header_tables.mysql almost starts with START TRANSACTION; and finishes with COMMIT; The problem is that there actually is a commit for each CREATE TABLE;
My suggestion is that you should drop the START TRANSACTION and COMMIT line, since it is more confusing and adds a false feeling of security. http://dev.mysql.com/doc/refman/5.0/en/innodb-implicit-command-or-rollback.html ====================================================================== ---------------------------------------------------------------------- aaron - 24-Mar-06 12:08 ---------------------------------------------------------------------- "The CREATE TABLE, CREATE DATABASE DROP DATABASE, and TRUNCATE TABLE statements cause an implicit commit beginning with MySQL 5.0.8." I've added a note indicating that the commands are redundant. I would prefer not to remove them, however. ---------------------------------------------------------------------- MagnusSundberg - 24-Mar-06 17:46 ---------------------------------------------------------------------- Sorry to reopen the issue, my beleif is that MySQL has always behaved like this. It is in the documentation from version 5.0.8. I have hade scripts that were not possible to rollback in version 4. These contained CREATE TEMPORARY TABLE, and I didn't understand why it was not possible to ROLLBACK until I read about the implicit commit for version 5. ---------------------------------------------------------------------- aaron - 29-Apr-06 04:09 ---------------------------------------------------------------------- Paul merged all of the creation scripts together and did indeed remove the transaction commands from the MySQL script. The bug is moot now. Issue History Date Modified Username Field Change ====================================================================== 31-Jan-06 12:02 MagnusSundberg New Issue 24-Mar-06 12:08 aaron Status new => resolved 24-Mar-06 12:08 aaron Fixed in Version => SVN Trunk 24-Mar-06 12:08 aaron Resolution open => fixed 24-Mar-06 12:08 aaron Assigned To => aaron 24-Mar-06 12:08 aaron Note Added: 0001048 24-Mar-06 17:46 MagnusSundberg Status resolved => feedback 24-Mar-06 17:46 MagnusSundberg Resolution fixed => reopened 24-Mar-06 17:46 MagnusSundberg Note Added: 0001056 29-Apr-06 04:09 aaron Status feedback => resolved 29-Apr-06 04:09 aaron Resolution reopened => fixed 29-Apr-06 04:09 aaron Note Added: 0001118 ======================================================================