Postgresql Using SQLite Using BerkeleyDB Using MySQL Connecting using a Database URL Multi-threaded applications Run-time database configuration Dynamically defining a database Connection Pooling Read Slaves written a number of blog posts about building applications and web-services with peewee (and usually Flask). If you’d like to see some “real-life” applications that use peewee, the following resources may for the local MySQL database my_db. More examples in the db_url documentation. Multi-threaded applications peewee stores the connection state in a thread local, so each thread gets its own separate connection

written a number of blog posts about building applications and web-services with peewee (and usually Flask). If you’d like to see some “real-life” applications that use peewee, the following resources may local MySQL database my_db. • More examples in the db_url documentation. 1.6.7 Multi-threaded applications peewee stores the connection state in a thread local, so each thread gets its own separate connection resolve any circular references that were found. 1.6.14 Adding Request Hooks When building web-applications, it is very important that you manage your database connections correctly. In this section I will

configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Async with Gevent Framework Integration Executing Queries Managing Transactions Database Errors connection pool, see the Connection pool section of the playhouse documentation. Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special Async has no effect one way or the other on SQLite databases. Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when

configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Async with Gevent Framework Integration Executing Queries Managing Transactions Database Errors connection pool, see the Connection pool section of the playhouse documentation. Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special Async has no effect one way or the other on SQLite databases. Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when

configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Framework Integration Executing Queries Managing Transactions Database Errors Logging queries connection pool, see the Connection pool section of the playhouse documentation. Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special test-suite [https://github.com/coleifer/peewee/tree/master/tests]. Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when

configuration Dynamically defining a database Connection Management Connection Pooling Testing Peewee Applications Async with Gevent Framework Integration Executing Queries Managing Transactions Database Errors connection pool, see the Connection pool section of the playhouse documentation. Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special Async has no effect one way or the other on SQLite databases. Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when

pool, see the Connection pool section of the playhouse documen- tation. 1.5.10 Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special has no effect one way or the other on SQLite databases. 1.5.12 Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when a pool of multiple Postgres connections, peewee will handle the connections correctly. Note: Applications that receive lots of traffic may benefit from using a connection pool to mitigate the cost of

pool, see the Connection pool section of the playhouse documen- tation. 1.6.10 Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special 1.6. Database 51 peewee Documentation, Release 3.3.0 1.6.12 Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when a pool of multiple Postgres connections, peewee will handle the connections correctly. Note: Applications that receive lots of traffic may benefit from using a connection pool to mitigate the cost of

pool, see the Connection pool section of the playhouse documen- tation. 1.6.10 Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special has no effect one way or the other on SQLite databases. 1.6.12 Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when a pool of multiple Postgres connections, peewee will handle the connections correctly. Note: Applications that receive lots of traffic may benefit from using a connection pool to mitigate the cost of

pool, see the Connection pool section of the playhouse documen- tation. 1.5.10 Testing Peewee Applications When writing tests for an application that uses Peewee, it may be desirable to use a special has no effect one way or the other on SQLite databases. 1.5.12 Framework Integration For web applications, it is common to open a connection when a request is received, and to close the connection when a pool of multiple Postgres connections, peewee will handle the connections correctly. Note: Applications that receive lots of traffic may benefit from using a connection pool to mitigate the cost of