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 recycled properly. Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 recycled properly. Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 recycled properly. Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 recycled properly. Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 recycled properly. Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 Documentation, Release 3.4.0 Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 recycled properly. Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 recycled properly. Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

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 response 14 Chapter 1. Contents: peewee Documentation, Release 3.6.0 Note: Peewee uses thread local storage to manage connection state, so this pattern can be used with multi-threaded WSGI servers. Making Documentation, Release 3.6.0 Thread Safety Peewee keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s

to a model with a non-integer primary key will have the ForeignKeyField use the same underlying storage type as the primary key they are related to. See full documentation on non-integer primary keys that specifies which database to use. then, any subclasses will automatically # use the correct storage. for more information, see: # http://charlesleifer.com/docs/peewee/peewee/models.html#model-api-smells-like-django database columns. Each field type has a corresponding SQL storage class (i.e. varchar, int), and conversion between python data types and underlying storage is handled transparently. When creating a Model class