~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/commit.rst

Committer: Monty Taylor
Date: 2011-03-10 18:18:24 UTC
mfrom: (2222.2.1 drizzle)
mto: This revision was merged to the branch mainline in revision 2228.
Revision ID: mordred@inaugust.com-20110310181824-mv5zqrahenb62y5i

Merge Mark: Documentation Edits

Show diffs side-by-side

added added

removed removed

docs/commit.rst

Calling COMMIT will cause the current transaction to save itself.

A COMMIT statement ends a transaction within Drizzle and makes all changes visible to other users. The order of events is typically to issue a START TRANSACTION statement, execute one or more SQL statements, and then issue a COMMIT statement. Alternatively, a ROLLBACK statement can be issued, which undoes all the work performed since START TRANSACTION was issued. A COMMIT statement will also release any existing savepoints that may be in use.

A COMMIT statement ends a transaction within Drizzle and makes all

changes visible to other users. The order of events is typically to

issue a START TRANSACTION statement, execute one or more SQL

statements, and then issue a COMMIT statement. Alternatively, a

ROLLBACK statement can be issued, which undoes all the work performed

since START TRANSACTION was issued. A COMMIT statement will also

release any existing savepoints that may be in use.

For example, DML statements do not implicitly commit the current transaction. If a user's DML statements have been used to update some data objects, and the updates need to be permanently recorded in the database, you can use the COMMIT command.

For example, DML statements do not implicitly commit the current

transaction. If a user's DML statements have been used to update some

data objects, and the updates need to be permanently recorded in the

database, you can use the COMMIT command.

An example:

Older »