ok
Direktori : /opt/alt/python38/lib64/python3.8/site-packages/playhouse/__pycache__/ |
Current File : //opt/alt/python38/lib64/python3.8/site-packages/playhouse/__pycache__/pool.cpython-38.pyc |
U S��W � @ s. d Z ddlZddlZddlZddlmZ ddlmZ ddlmZ e�d�Z dd� Z G d d � d e�ZG dd� dee�Z G d d� de�ZG dd� dee�Zz"ddlmZ G dd� dee�ZW n ek r� Y nX G dd� de�ZG dd� dee�Zz"ddlmZ G dd� dee�ZW n ek �r( Y nX dS )ap Lightweight connection pooling for peewee. In a multi-threaded application, up to `max_connections` will be opened. Each thread (or, if using gevent, greenlet) will have it's own connection. In a single-threaded application, only one connection will be created. It will be continually recycled until either it exceeds the stale timeout or is closed explicitly (using `.manual_close()`). By default, all your application needs to do is ensure that connections are closed when you are finished with them, and they will be returned to the pool. For web applications, this typically means that at the beginning of a request, you will open a connection, and when you return a response, you will close the connection. Simple Postgres pool example code: # Use the special postgresql extensions. from playhouse.pool import PooledPostgresqlExtDatabase db = PooledPostgresqlExtDatabase( 'my_app', max_connections=32, stale_timeout=300, # 5 minutes. user='postgres') class BaseModel(Model): class Meta: database = db That's it! In some situations you may want to manage your connections more explicitly. Since peewee stores the active connection in a threadlocal, this typically would mean that there could only ever be one connection open per thread. For most applications this is desirable, but if you would like to manually manage multiple connections you can create an *ExecutionContext*. Execution contexts allow finer-grained control over managing multiple connections to the database. When an execution context is initialized (either as a context manager or as a decorated function), a separate connection will be used for the duration of the wrapped block. You can also choose whether to wrap the block in a transaction. Execution context examples (using above `db` instance): with db.execution_context() as ctx: # A new connection will be opened or pulled from the pool of available # connections. Additionally, a transaction will be started. user = User.create(username='charlie') # When the block ends, the transaction will be committed and the connection # will be returned to the pool. @db.execution_context(with_transaction=False) def do_something(foo, bar): # When this function is called, a separate connection is made and will # be closed when the function returns. � N)� MySQLDatabase)�PostgresqlDatabase)�SqliteDatabasezpeewee.poolc C s"