Speeding up Bulk Inserts Transactions Context manager Decorator Nesting Transactions Explicit transaction Autocommit Mode Playhouse, extensions to Peewee Sqlite Extensions SqliteQ Sqlite User-Defined Utils pskel Flask Utils API Reference Models Fields Query Types Database and its subclasses Transaction, Savepoint and ExecutionContext Metadata Types Misc Hacks Optimistic Locking Top object per group so if the username is taken the database will raise an IntegrityError. try: with database.transaction(): # Attempt to create the user. If the username is taken, due to the # unique

constraint, so if the username is taken the database will raise an IntegrityError. try: with database.transaction(): # Attempt to create the user. If the username is taken, due to the # unique constraint, the up with duplicate rows: user = get_object_or_404(User, username=username) try: with database.transaction(): Relationship.create( 14 Chapter 1. Contents: peewee Documentation, Release 2.10.2 from_u search with BM25 ranking. • Support for custom functions, aggregates and collations • Advanced transaction support • And more! If you would like to use these awesome features, use the SqliteExtDatabase

Speeding up Bulk Inserts Transactions Context manager Decorator Nesting Transactions Explicit transaction Autocommit Mode Changes in 3.0 Backwards-incompatible New stuff API Documentation Database so if the username is taken the database will raise an IntegrityError. try: with database.transaction(): # Attempt to create the user. If the username is taken, due to the # unique with duplicate rows: user = get_object_or_404(User, username=username) try: with database.transaction(): Relationship.create( from_user=get_current_user(), to_user=user)

Speeding up Bulk Inserts Transactions Context manager Decorator Nesting Transactions Explicit transaction Autocommit Mode Changes in 3.0 Backwards-incompatible New stuff API Documentation Database so if the username is taken the database will raise an IntegrityError. try: with database.transaction(): # Attempt to create the user. If the username is taken, due to the # unique with duplicate rows: user = get_object_or_404(User, username=username) try: with database.transaction(): Relationship.create( from_user=get_current_user(), to_user=user)

constraint, so if the username is taken the database will raise an IntegrityError. try: with database.transaction(): # Attempt to create the user. If the username is taken, due to the # unique constraint, the up with duplicate rows: user = get_object_or_404(User, username=username) try: with database.transaction(): Relationship.create( from_user=get_current_user(), to_user=user) except IntegrityError: pass table_function() • For even more SQLite extensions, see SQLite Extensions Set locking mode for transaction SQLite transactions can be opened in three different modes: • Deferred (default) - only acquires

constraint, so if the username is taken the database will raise an IntegrityError. try: with database.transaction(): # Attempt to create the user. If the username is taken, due to the # unique constraint, the up with duplicate rows: user = get_object_or_404(User, username=username) try: with database.transaction(): Relationship.create( from_user=get_current_user(), to_user=user) except IntegrityError: pass table_function() • For even more SQLite extensions, see SQLite Extensions Set locking mode for transaction SQLite transactions can be opened in three different modes: • Deferred (default) - only acquires

Speeding up Bulk Inserts Transactions Context manager Decorator Nesting Transactions Explicit transaction Autocommit Mode Changes in 3.0 Backwards-incompatible New stuff API Documentation Database so if the username is taken the database will raise an IntegrityError. try: with database.transaction(): # Attempt to create the user. If the username is taken, due to the # unique with duplicate rows: user = get_object_or_404(User, username=username) try: with database.transaction(): Relationship.create( from_user=get_current_user(), to_user=user)

table_function() • For even more SQLite extensions, see SQLite Extensions Set locking mode for transaction SQLite transactions can be opened in three different modes: • Deferred (default) - only acquires deferred until actually needed, it is possible that another thread or process could create a separate transaction and write to the database after the BEGIN on the current thread has executed. • Immediate - a immediately. In this mode, no other database may write to the database or open an immediate or exclusive transaction. Other processes can continue to read from the database, however. • Exclusive - opens an exclusive

table_function() For even more SQLite extensions, see SQLite Extensions Set locking mode for transaction SQLite transactions can be opened in three different modes: Deferred (default) - only acquires deferred until actually needed, it is possible that another thread or process could create a separate transaction and write to the database after the BEGIN on the current thread has executed. Immediate - a reserved immediately. In this mode, no other database may write to the database or open an immediate or exclusive transaction. Other processes can continue to read from the database, however. Exclusive - opens an exclusive

table_function() • For even more SQLite extensions, see SQLite Extensions Set locking mode for transaction SQLite transactions can be opened in three different modes: • Deferred (default) - only acquires deferred until actually needed, it is possible that another thread or process could create a separate transaction and write to the database after the BEGIN on the current thread has executed. • Immediate - a immediately. In this mode, no other database may write to the database or open an immediate or exclusive transaction. Other processes can continue to read from the database, however. • Exclusive - opens an exclusive