Wählen Sie Ihren SQL-Server:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Neuheiten abonnieren
Partners
Testimonials
Mario Figueiredo: "I can safely forget all I know about SQL when using SQLite Maestro. It is that easy and intuitive to use. It is also nicely drawn with an easy and appealing interface that makes the sometimes boring tasks of database maintenance and administration more endurable.
The decision to support the non-commercial use of your software with a lower price is absolutely worth mentioning. For that alone, I thank you. For everything else, I say keep up the good work".
Jacob Lyohne, Director of Development: "Regarding implementation, it is pretty self-explanatory and the SQLite Maestro manual is helpful for review and reference. We also found the on-line documentation useful and the software support staff readily available to answer our questions. Reports are very easy and quick to run and can be broken down into any number of statistical combinations".

More

Add your opinion

Customers
Download Kaufen

SQLite Maestro online Help

  Return to chapter overview  

BEGIN TRANSACTION

sql-statement ::=

BEGIN [TRANSACTION [name]] [ON CONFLICT conflict-algorithm]

sql-statement ::=

END [TRANSACTION [name]]

sql-statement ::=

COMMIT [TRANSACTION [name]]

sql-statement ::=

ROLLBACK [TRANSACTION [name]]

Beginning in version 2.0, SQLite supports transactions with rollback and atomic commit.

No changes can be made to the database except within a transaction. Any command that changes the database (basically, any SQL command other than SELECT) will automatically starts a transaction if one is not already in effect. Automatically started transactions are committed at the conclusion of the command.

 

Transactions can be started manually using the BEGIN command. Such transactions usually persist until the next COMMIT or ROLLBACK command. But a transaction will also ROLLBACK if the database is closed or if an error occurs and the ROLLBACK conflict resolution algorithm is specified. See the documentation on the ON CONFLICT clause for additional information about the ROLLBACK conflict resolution algorithm.

The optional ON CONFLICT clause at the end of a BEGIN statement can be used to changed the default conflict resolution algorithm. The normal default is ABORT. If an alternative is specified by the ON CONFLICT clause of a BEGIN, then that alternative is used as the default for all commands within the transaction. The default algorithm is overridden by ON CONFLICT clauses on individual constraints within the CREATE TABLE or CREATE INDEX statements and by the OR clauses on COPY, INSERT, and UPDATE commands.



  Return to chapter overview