MySQLDatabase): pass db = MyRetryDB('my_app') Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

MySQLDatabase): pass db = MyRetryDB('my_app') 1.6.20 Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested Documentation, Release 2.10.2 1.7.3 Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

these error classes extend PeeweeException. Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

these error classes extend PeeweeException. Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

these error classes extend PeeweeException. Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

these error classes extend PeeweeException. Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

error classes extend PeeweeException. 1.5.16 Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. 1.6.3 Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

error classes extend PeeweeException. 1.6.16 Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. 1.7.4 Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

error classes extend PeeweeException. 1.6.16 Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. 1.7.4 Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific

these error classes extend PeeweeException. Logging queries All queries are logged to the peewee namespace using the standard library logging module. Queries are logged using the DEBUG level. If you’re interested migrations docs for details. Model options and table metadata In order not to pollute the model namespace, model-specific configuration is placed in a special class called Meta (a convention borrowed from to Peewee Peewee comes with numerous extension modules which are collected under the playhouse namespace. Despite the silly name, there are some very useful extensions, particularly those that expose vendor-specific