peewee Documentation Release 2.10.2after_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 db_url documentation. Multi-threaded applications peewee stores the connection state in a thread local, so each thread gets its own separate connection. If you prefer to manage the connections yourself, you request, and close the connection when you return a response. Because connection state is stored in a thread-local, you do not need to worry about juggling connection objects – peewee will handle it for you0 码力 | 275 页 | 276.96 KB | 1 年前3
peewee Documentation
Release 2.10.2@app.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 documentation. 1.6.7 Multi-threaded applications peewee stores the connection state in a thread local, so each thread gets its own separate connection. If you prefer to manage the connections yourself, you request, and close the connection when you return a response. Because connection state is stored in a thread-local, you do not need to worry about juggling connection objects – peewee will handle it for you0 码力 | 221 页 | 844.06 KB | 1 年前3
peewee Documentation Release 3.0.0after_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 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 lock 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 own0 码力 | 319 页 | 361.50 KB | 1 年前3
peewee Documentation
Release 3.5.0after_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 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 lock 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 own0 码力 | 347 页 | 380.80 KB | 1 年前3
peewee Documentation Release 3.4.0after_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 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 lock 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 own0 码力 | 349 页 | 382.34 KB | 1 年前3
peewee Documentation Release 3.1.0after_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 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 lock 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 own0 码力 | 332 页 | 370.77 KB | 1 年前3
peewee Documentation
Release 3.5.0@app.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 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 lock 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 own0 码力 | 282 页 | 1.02 MB | 1 年前3
peewee Documentation
Release 3.3.0@app.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 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 lock 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 own0 码力 | 280 页 | 1.02 MB | 1 年前3
peewee Documentation
Release 3.4.0@app.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 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 lock 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 own0 码力 | 284 页 | 1.03 MB | 1 年前3
peewee Documentation Release 3.6.0after_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 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 lock 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 own0 码力 | 377 页 | 399.12 KB | 1 年前3
共 16 条
- 1
- 2













