Existing Databases Adding Request Hooks Additional connection initialization Advanced Connection Management Using multiple databases Database Errors Automatic Reconnect Logging queries Generating skeleton that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its after_request(response): database.close() return response Note Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making

using a Database URL Run-time database configuration Dynamically defining a database Connection Management Connection Pooling Framework Integration Executing Queries Managing Transactions Database Errors that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its after_request(response): database.close() return response Note Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making

using a Database URL Run-time database configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Async with Gevent Framework Integration Executing that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its after_request(response): database.close() return response Note Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making

using a Database URL Run-time database configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Framework Integration Executing Queries Managing that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its after_request(response): database.close() return response Note Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making

that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its fields after_request def after_request(response): database.close() return response Note: Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. 1.3. Example see the Adding Request Hooks section. Note: For advanced connection management techniques, see the advanced connection management section. To use this database with your models, set the database attribute

using a Database URL Run-time database configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Async with Gevent Framework Integration Executing that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its after_request(response): database.close() return response Note Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making

that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its fields after_request def after_request(response): database.close() return response Note: Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making instead use Database.init(). See Run-time database configuration for more details. 1.6.8 Connection Management To open a connection to a database, use the Database.connect() method: >>> db = SqliteDatabase(':memory:')

that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its fields after_request def after_request(response): database.close() return response Note: Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making configuration for more details. 1.6. Database 47 peewee Documentation, Release 3.4.0 1.6.8 Connection Management To open a connection to a database, use the Database.connect() method: >>> db = SqliteDatabase(':memory:')

using a Database URL Run-time database configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Async with Gevent Framework Integration Executing that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its after_request(response): database.close() return response Note Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making

that specifies which database to use. then, any subclasses will automatically # use the correct storage. class BaseModel(Model): class Meta: database = database # the user model specifies its fields after_request def after_request(response): database.close() return response Note: Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making instead use Database.init(). See Run-time database configuration for more details. 1.5.8 Connection Management To open a connection to a database, use the Database.connect() method: >>> db = SqliteDatabase(':memory:')