using atomic(), the outer-most call will be wrapped in a transaction, and any nested calls will use savepoints. with db.atomic() as txn: perform_operation() with db.atomic() as nested_txn: perform_another_operation() Peewee supports nested transactions through the use of savepoints (for more information, see savepoint()). Explicit transaction If you wish to explicitly run code in a transaction that you use atomic(). Explicit Savepoints Just as you can explicitly create transactions, you can also explicitly create savepoints using the savepoint() method. Savepoints must occur within a transaction

and then can be used to: Open and close connections. Execute queries. Manage transactions (and savepoints). Introspect tables, columns, indexes, and constraints. Model integration Peewee comes with support using atomic(), the outer-most call will be wrapped in a transaction, and any nested calls will use savepoints. with db.atomic() as txn: perform_operation() with db.atomic() as nested_txn: perform_another_operation() Peewee supports nested transactions through the use of savepoints (for more information, see savepoint()). Explicit transaction If you wish to explicitly run code in a transaction

and then can be used to: Open and close connections. Execute queries. Manage transactions (and savepoints). Introspect tables, columns, indexes, and constraints. Model integration Peewee comes with support using atomic(), the outer-most call will be wrapped in a transaction, and any nested calls will use savepoints. with db.atomic() as txn: perform_operation() with db.atomic() as nested_txn: perform_another_operation() Peewee supports nested transactions through the use of savepoints (for more information, see savepoint()). Explicit transaction If you wish to explicitly run code in a transaction

and then can be used to: Open and close connections. Execute queries. Manage transactions (and savepoints). Introspect tables, columns, indexes, and constraints. Model integration Peewee comes with support using atomic(), the outer-most call will be wrapped in a transaction, and any nested calls will use savepoints. with db.atomic() as txn: perform_operation() with db.atomic() as nested_txn: perform_another_operation() Peewee supports nested transactions through the use of savepoints (for more information, see savepoint()). Explicit transaction If you wish to explicitly run code in a transaction

and then can be used to: Open and close connections. Execute queries. Manage transactions (and savepoints). Introspect tables, columns, indexes, and constraints. Peewee comes with support for SQLite, using atomic(), the outer-most call will be wrapped in a transaction, and any nested calls will use savepoints. with db.atomic() as txn: perform_operation() with db.atomic() as nested_txn: perform_another_operation() Peewee supports nested transactions through the use of savepoints (for more information, see savepoint()). Explicit transaction If you wish to explicitly run code in a transaction

and then can be used to: Open and close connections. Execute queries. Manage transactions (and savepoints). Introspect tables, columns, indexes, and constraints. Peewee comes with support for SQLite, using atomic(), the outer-most call will be wrapped in a transaction, and any nested calls will use savepoints. with db.atomic() as txn: perform_operation() with db.atomic() as nested_txn: perform_another_operation() Peewee supports nested transactions through the use of savepoints (for more information, see savepoint()). Explicit transaction If you wish to explicitly run code in a transaction

the database, unless a transaction is active. See below for details. Django uses transactions or savepoints automatically to guarantee the integrity of ORM operations that require multiple queries, especially produces an exception, Django rolls back the transaction. You may perform subtransactions using savepoints in your view code, typically with the atomic() context manager. However, at the end of the view or rolls back the transaction when exiting the outermost block. You can disable the creation of savepoints for inner blocks by setting the savepoint argument to False. If an exception occurs, Django will

the database, unless a transaction is active. See below for details. Django uses transactions or savepoints automatically to guarantee the integrity of ORM operations that require multiple queries, especially produces an exception, Django rolls back the transaction. You may perform subtransactions using savepoints in your view code, typically with the atomic() context manager. However, at the end of the view or rolls back the transaction when exiting the outermost block. You can disable the creation of savepoints for inner blocks by setting the savepoint argument to False. If an exception occurs, Django will

the database, unless a transaction is active. See below for details. Django uses transactions or savepoints automatically to guarantee the integrity of ORM operations that require multiple queries, especially produces an exception, Django rolls back the transaction. You may perform subtransactions using savepoints in your view code, typically with the atomic() context manager. However, at the end of the view or rolls back the transaction when exiting the outermost block. You can disable the creation of savepoints for inner blocks by setting the savepoint argument to False. If an exception occurs, Django will

the database, unless a transaction is active. See below for details. Django uses transactions or savepoints automatically to guarantee the integrity of ORM operations that require multiple queries, especially produces an exception, Django rolls back the transaction. You may perform subtransactions using savepoints in your view code, typically with the atomic() context manager. However, at the end of the view or rolls back the transaction when exiting the outermost block. You can disable the creation of savepoints for inner blocks by setting the savepoint argument to False. If an exception occurs, Django will