+ hj4^RIHt^RIt^RIHt^RIHt^RIHt^RIHt^RIHt^RIH t ^R IH t ^R IH t ^R I H t ^R I Ht]P'd ^R IHt^RIHt!RR] P(] ,4tR#)) annotationsN)Any)Optional)Type)Union)ConnectionPoolEntry)Pool)PoolProxiedConnection)PoolResetState)event)util)Engine)DBAPIConnectionc$]tRt^tRtRt]t]P!R4] RRl44t ] RRl4t RR lt R R ltR R ltRRlt]P$!RRR.R4RRl4tRRltRRltRRltRRltRRltR tR!#)" PoolEventsazAvailable events for :class:`_pool.Pool`. The methods here define the name of an event as well as the names of members that are passed to listener functions. When using an :class:`.Engine` object created via :func:`_sa.create_engine` (or indirectly via :func:`.create_async_engine`), :class:`.PoolEvents` listeners are expected to be registered in terms of the :class:`.Engine`, which will direct the listeners to the :class:`.Pool` contained within:: from sqlalchemy import create_engine from sqlalchemy import event engine = create_engine("postgresql+psycopg2://scott:tiger@localhost/test") @event.listens_for(engine, "checkout") def my_on_checkout(dbapi_conn, connection_rec, connection_proxy): "handle an on checkout event" :class:`.PoolEvents` may also be registered with the :class:`_pool.Pool` class, with the :class:`.Engine` class, as well as with instances of :class:`_pool.Pool`. .. tip:: Registering :class:`.PoolEvents` with the :class:`.Engine`, if present, is recommended since the :meth:`.Engine.dispose` method will carry along event listeners from the old pool to the new pool. SomeEngineOrPoolzsqlalchemy.enginec$V^8dQhRRRRRR/#)targetz-Union[Pool, Type[Pool], Engine, Type[Engine]] identifierstrreturnz!Optional[Union[Pool, Type[Pool]]])formats"Q/var/www/html/bestweb/venv/lib/python3.14/site-packages/sqlalchemy/pool/events.py __annotate__PoolEvents.__annotate__Bs(= + c \P'g%\PPP p\ V\4'd3\VX4'd\#\V\4'gQhV#\ VX4'd VP#\ V\4'dV#\VR4'dVP4R#R#)_no_async_engine_eventsN) typing TYPE_CHECKINGr preloadedenginer isinstancetype issubclassr poolhasattrr )clsrrrs&&& r _accept_withPoolEvents._accept_with@s###^^**11F fd # #&&)) !&$////  ' ';;   % %M V6 7 7  * * ,rc$V^8dQhRRRRRR/#)r event_keyzevent._EventKey[Pool]kwrrNoner)rs"rrrZs( $ $( $ $  $rc zVPpVPRVP4VP!R/VBR#)asyncioNr)dispatch_target setdefault _is_asyncio base_listen)r*r.r/rs&&, r_listenPoolEvents._listenYs4 ** i!3!34##rc$V^8dQhRRRRRR/#rdbapi_connectionrconnection_recordrrr0r)rs"rrres(  ) /    rc R#)aCalled at the moment a particular DBAPI connection is first created for a given :class:`_pool.Pool`. This event allows one to capture the point directly after which the DBAPI module-level ``.connect()`` method has been used in order to produce a new DBAPI connection. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. Nrselfr;r<s&&&rconnectPoolEvents.connecterc$V^8dQhRRRRRR/#r:r)rs"rrrys(  ) /    rc R#)aCalled exactly once for the first time a DBAPI connection is checked out from a particular :class:`_pool.Pool`. The rationale for :meth:`_events.PoolEvents.first_connect` is to determine information about a particular series of database connections based on the settings used for all connections. Since a particular :class:`_pool.Pool` refers to a single "creator" function (which in terms of a :class:`_engine.Engine` refers to the URL and connection options used), it is typically valid to make observations about a single connection that can be safely assumed to be valid about all subsequent connections, such as the database version, the server and client encoding settings, collation settings, and many others. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. Nrr>s&&&r first_connectPoolEvents.first_connectyrBrc(V^8dQhRRRRRRRR/#) rr;rr<rconnection_proxyr rr0r)rs"rrrs2  ) / 0    rc R#)aCalled when a connection is retrieved from the Pool. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. :param connection_proxy: the :class:`.PoolProxiedConnection` object which will proxy the public interface of the DBAPI connection for the lifespan of the checkout. If you raise a :class:`~sqlalchemy.exc.DisconnectionError`, the current connection will be disposed and a fresh connection retrieved. Processing of all checkout listeners will abort and restart using the new connection. .. seealso:: :meth:`_events.ConnectionEvents.engine_connect` - a similar event which occurs upon creation of a new :class:`_engine.Connection`. Nr)r?r;r<rHs&&&&rcheckoutPoolEvents.checkoutrBrc$V^8dQhRRRRRR/#)rr;zOptional[DBAPIConnection]r<rrr0r)rs"rrrs(  3 /    rc R#)aCalled when a connection returns to the pool. Note that the connection may be closed, and may be None if the connection has been invalidated. ``checkin`` will not be called for detached connections. (They do not return to the pool.) :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. Nrr>s&&&rcheckinPoolEvents.checkinrBrz2.0r;r<c VV3#)Nr)r;r< reset_states&&&rPoolEvents.s  B rc(V^8dQhRRRRRRRR/#) rr;rr<rrQr rr0r)rs"rrrs26 6 )6 /6 $ 6  6 rc R#)aCalled before the "reset" action occurs for a pooled connection. This event represents when the ``rollback()`` method is called on the DBAPI connection before it is returned to the pool or discarded. A custom "reset" strategy may be implemented using this event hook, which may also be combined with disabling the default "reset" behavior using the :paramref:`_pool.Pool.reset_on_return` parameter. The primary difference between the :meth:`_events.PoolEvents.reset` and :meth:`_events.PoolEvents.checkin` events are that :meth:`_events.PoolEvents.reset` is called not just for pooled connections that are being returned to the pool, but also for connections that were detached using the :meth:`_engine.Connection.detach` method as well as asyncio connections that are being discarded due to garbage collection taking place on connections before the connection was checked in. Note that the event **is not** invoked for connections that were invalidated using :meth:`_engine.Connection.invalidate`. These events may be intercepted using the :meth:`.PoolEvents.soft_invalidate` and :meth:`.PoolEvents.invalidate` event hooks, and all "connection close" events may be intercepted using :meth:`.PoolEvents.close`. The :meth:`_events.PoolEvents.reset` event is usually followed by the :meth:`_events.PoolEvents.checkin` event, except in those cases where the connection is discarded immediately after reset. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. :param reset_state: :class:`.PoolResetState` instance which provides information about the circumstances under which the connection is being reset. .. versionadded:: 2.0 .. seealso:: :ref:`pool_reset_on_return` :meth:`_events.ConnectionEvents.rollback` :meth:`_events.ConnectionEvents.commit` Nr)r?r;r<rQs&&&&rresetPoolEvents.resetrBrc(V^8dQhRRRRRRRR/# rr;rr<r exceptionzOptional[BaseException]rr0r)rs"rrrs2  ) / +    rc R#)aCalled when a DBAPI connection is to be "invalidated". This event is called any time the :meth:`.ConnectionPoolEntry.invalidate` method is invoked, either from API usage or via "auto-invalidation", without the ``soft`` flag. The event occurs before a final attempt to call ``.close()`` on the connection occurs. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. :param exception: the exception object corresponding to the reason for this invalidation, if any. May be ``None``. .. seealso:: :ref:`pool_connection_invalidation` Nrr?r;r<rZs&&&&r invalidatePoolEvents.invalidaterBrc(V^8dQhRRRRRRRR/#rYr)rs"rrr$s2  ) / +    rc R#)aCalled when a DBAPI connection is to be "soft invalidated". This event is called any time the :meth:`.ConnectionPoolEntry.invalidate` method is invoked with the ``soft`` flag. Soft invalidation refers to when the connection record that tracks this connection will force a reconnect after the current connection is checked in. It does not actively close the dbapi_connection at the point at which it is called. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. :param exception: the exception object corresponding to the reason for this invalidation, if any. May be ``None``. Nrr\s&&&&rsoft_invalidatePoolEvents.soft_invalidate$rBrc$V^8dQhRRRRRR/#r:r)rs"rrr@s(  ) /    rc R#)amCalled when a DBAPI connection is closed. The event is emitted before the close occurs. The close of a connection can fail; typically this is because the connection is already closed. If the close operation fails, the connection is discarded. The :meth:`.close` event corresponds to a connection that's still associated with the pool. To intercept close events for detached connections use :meth:`.close_detached`. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. Nrr>s&&&rclosePoolEvents.close@rBrc$V^8dQhRRRRRR/#r:r)rs"rrrYs(  ) /    rc R#)a~Called when a DBAPI connection is "detached" from a pool. This event is emitted after the detach occurs. The connection is no longer associated with the given connection record. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. :param connection_record: the :class:`.ConnectionPoolEntry` managing the DBAPI connection. Nrr>s&&&rdetachPoolEvents.detachYrBrc V^8dQhRRRR/#)rr;rrr0r)rs"rrrks     4  rc R#)alCalled when a detached DBAPI connection is closed. The event is emitted before the close occurs. The close of a connection can fail; typically this is because the connection is already closed. If the close operation fails, the connection is discarded. :param dbapi_connection: a DBAPI connection. The :attr:`.ConnectionPoolEntry.dbapi_connection` attribute. Nr)r?r;s&&rclose_detachedPoolEvents.close_detachedkrBrrN)__name__ __module__ __qualname____firstlineno____doc___target_class_docr _dispatch_targetr preload_module classmethodr+r7r@rErJrNr _legacy_signaturerVr]rarerirm__static_attributes__rrrrrsB+ ,-.. $ $ ( : : &  01 6 6 p < 8 2 $   rr) __future__rr!rrrrbaserr r r r r r"r$rengine.interfacesrEventsrrrrrsT# %'  3\ d#\ r