[dba-SQLServer] Upgrade to MySql

Stuart McLachlan stuart at lexacorp.com.pg
Thu Aug 12 19:11:50 CDT 2010


On 12 Aug 2010 at 14:52, Jim Lawrence wrote:

> There are a few good reasons for not going to MySQL. 
> 
> For example you can not roll back a transaction or series of
> transactions. For any application, that is at all like accounting,
> that is a big minus. 

http://dev.mysql.com/doc/refman/5.0/en/commit.html

MySQL 5.0 Reference Manual :: 12 SQL Statement Syntax :: 12.3 MySQL Transactional and 
Locking Statements :: 12.3.1 START TRANSACTION, COMMIT, and ROLLBACK Syntax

12.3.1. START TRANSACTION, COMMIT, and ROLLBACK Syntax

START TRANSACTION [WITH CONSISTENT SNAPSHOT] | BEGIN [WORK]
COMMIT [WORK] [AND [NO] CHAIN] [[NO] RELEASE]
ROLLBACK [WORK] [AND [NO] CHAIN] [[NO] RELEASE]
SET autocommit = {0 | 1}

The START TRANSACTION or BEGIN statement begins a new transaction. COMMIT 
commits the current transaction, making its changes permanent. ROLLBACK rolls back the 
current transaction, canceling its changes. The SET autocommit statement disables or 
enables the default autocommit mode for the current session.

Beginning with MySQL 5.0.3, the optional WORK keyword is supported for COMMIT and 
ROLLBACK, as are the CHAIN and RELEASE clauses. CHAIN and RELEASE can be used 
for additional control over transaction completion. The value of the completion_type system 
variable determines the default completion behavior. 



More information about the dba-SQLServer mailing list