Difference between revisions of "Portable SQL/Statements/Transactions"
From Linuxnetworks
(→Starting transactions) |
|||
| Line 32: | Line 32: | ||
|} | |} | ||
| − | The statement which fits for the most popular Open Source databases | + | The statement which fits for the most popular Open Source databases and which is understood by MySQL, PostgreSQL and SQLite: |
| + | |||
| + | BEGIN | ||
== Saving changes == | == Saving changes == | ||
Revision as of 18:56, 17 May 2007
Starting transactions
The ANSI SQL standard defines a statement for starting new transactions:
START TRANSACTION
Unfortunately, database vendors use various different statements for starting transactions and there is no single string that fits for all.
| Database | Statement |
|---|---|
| Firebird | SET TRANSACTION |
| MySQL | BEGIN [WORK], START TRANSACTION (4.0.11) |
| Oracle | SET TRANSACTION ISOLATION LEVEL READ COMMITTED |
| PostgreSQL | BEGIN, SET TRANSACTION mode |
| SQLite | BEGIN [TRANSACTION] |
| SQL Server | BEGIN TRANSACTION |
| Sybase ASE | BEGIN TRANSACTION |
The statement which fits for the most popular Open Source databases and which is understood by MySQL, PostgreSQL and SQLite:
BEGIN
Saving changes
Making the changes done within a transaction permanent is easily done with a single statement for all databases:
COMMIT
Discarding changes
To undo all changes done within a transaction is as easy as committing them. A single statement for all databases exists:
ROLLBACK
Back to Overview
