byp4a55 professor6T9

Linux SamCT211 4.4.302+ #86009 SMP Wed Nov 26 18:19:20 CST 2025 x86_64
nginx/1.23.1
192.168.4.211

events.cpython-38.pyc

�����}�hؗ���������������������@���s`��d�Z�ddlZddlmZ�ddlmZ�ddlmZ�ddlmZ�ddlm	Z	�dd	l
mZ�dd
lm
Z
�ddlmZ�ddlmZ�d
dlmZ�d
dlmZ�d
dlmZ�d
dlmZ�G�dd��dej�ZG�dd��de�ZG�dd��dej�ZG�dd��dej�ZG�dd��de�ZG�dd��dej�ZG�dd��de�Ze ��Z!G�d d!��d!ej�Z"G�d"d#��d#ej�Z#G�d$d%��d%ej�Z$dS�)&zORM event interfaces.

�����N����)�instrumentation)�
interfaces)�	mapperlib)�QueryableAttribute��_mapper_or_none)�Query)�scoped_session)�Session)�sessionmaker����)�event)�exc)�util)�inspect_getfullargspecc�����������������������s`���e�Zd�ZdZdZejZedd���Z	eddd��Z
e��fdd	��Zd
d��Zdd
��Z
dd��Z���ZS�)�InstrumentationEventsa��Events related to class instrumentation events.

The listeners here support being established against
    any new style class, that is any object that is a subclass
    of 'type'.  Events will then be fired off for events
    against that class.  If the "propagate=True" flag is passed
    to event.listen(), the event will fire off for subclasses
    of that class as well.

The Python ``type`` builtin is also accepted as a target,
    which when used has the effect of events being emitted
    for all classes.

Note the "propagate" flag here is defaulted to ``True``,
    unlike the other class level events where it defaults
    to ``False``.  This means that new subclasses will also
    be the subject of these events, when a listener
    is established on a superclass.

Z
SomeBaseClassc�����������������C���s���t�|t�rt|�S�d�S�d�S��N)�
isinstance�type�_InstrumentationEventsHold��cls�target��r����</tmp/pip-target-hu2ovxdm/lib/python/sqlalchemy/orm/events.py�_accept_with5���s����
z"InstrumentationEvents._accept_withTc��������������������s`���|j�|j|j����������fdd����fdd�}t��j|��|�tj��	��j
f�|��d�S�)Nc��������������������s@������}�r"t�|�|�r"��|�f|���S��s<|�|kr<��|�f|���S�d�S�r���)�
issubclass)Z
target_cls�argZ
listen_cls)�fn�	propagater���r���r����listenD���s
����z-InstrumentationEvents._listen.<locals>.listenc��������������������s,���t�j�d����tj�}ttjj����|��d�S�r���)r����registryZ	_EventKeyr����_instrumentation_factory�getattr�dispatch�remove)�ref�key)�
identifierr!���r���r���r&���K���s��������z-InstrumentationEvents._listen.<locals>.remove)�dispatch_targetr)����
_listen_fn�weakrefr'����class_�with_dispatch_targetr���r#����with_wrapper�base_listen)r����	event_keyr ����kwr&���r���)r���r)���r!���r ���r���r����_listen<���s�����
���zInstrumentationEvents._listenc��������������������s���t�t|������tjj����d�S�r���)�superr����_clearr���r#���r%����r�����	__class__r���r���r5���\���s����zInstrumentationEvents._clearc�����������������C���s���dS�)z�Called after the given class is instrumented.

To get at the :class:`.ClassManager`, use
        :func:`.manager_of_class`.

Nr�����selfr���r���r���r����class_instrumenta���s����z&InstrumentationEvents.class_instrumentc�����������������C���s���dS�)z�Called before the given class is uninstrumented.

To get at the :class:`.ClassManager`, use
        :func:`.manager_of_class`.

Nr���r9���r���r���r����class_uninstrumenti���s����z(InstrumentationEvents.class_uninstrumentc�����������������C���s���dS�)z)Called when an attribute is instrumented.Nr���)r:���r���r(����instr���r���r����attribute_instrumentq���s����z*InstrumentationEvents.attribute_instrument)T)�__name__�
__module__�__qualname__�__doc__�_target_class_docr���ZInstrumentationFactory�_dispatch_target�classmethodr���r3���r5���r;���r<���r>����
__classcell__r���r���r7���r���r������s���
r���c�������������������@���s"���e�Zd�ZdZdd��Ze�e�ZdS�)r���zwtemporary marker object used to transfer from _accept_with() to
    _listen() on the InstrumentationEvents class.

c�����������������C���s
���||�_�d�S�r����r-����r:���r-���r���r���r����__init__{���s����z#_InstrumentationEventsHold.__init__N)	r?���r@���rA���rB���rI���r����
dispatcherr���r%���r���r���r���r���r���u���s���r���c�����������������������s����e�Zd�ZdZdZejZedd���Z	ee
�d�dd����Zedd	d
��Z
e��fdd��Zd
d��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd��Z���ZS�) �InstanceEventsa���Define events specific to object lifecycle.

e.g.::

from sqlalchemy import event

def my_load_listener(target, context):
            print("on load!")

event.listen(SomeClass, 'load', my_load_listener)

Available targets include:

* mapped classes
    * unmapped superclasses of mapped or to-be-mapped classes
      (using the ``propagate=True`` flag)
    * :class:`_orm.Mapper` objects
    * the :class:`_orm.Mapper` class itself and the :func:`.mapper`
      function indicate listening for all mappers.

Instance events are closely related to mapper events, but
    are more specific to the instance and its instrumentation,
    rather than its system of persistence.

When using :class:`.InstanceEvents`, several modifiers are
    available to the :func:`.event.listen` function.

:param propagate=False: When True, the event listener should
       be applied to all inheriting classes as well as the
       class which is the target of this listener.
    :param raw=False: When True, the "target" argument passed
       to applicable event listener functions will be the
       instance's :class:`.InstanceState` management
       object, rather than the mapped instance itself.
    :param restore_load_context=False: Applies to the
       :meth:`.InstanceEvents.load` and :meth:`.InstanceEvents.refresh`
       events.  Restores the loader context of the object when the event
       hook is complete, so that ongoing eager load operations continue
       to target the object appropriately.  A warning is emitted if the
       object is moved to a new loader context from within one of these
       events if this flag is not set.

.. versionadded:: 1.3.14

�	SomeClassc�����������������C���s���t��||��d�S�r���)�_InstanceEventsHold�populate)r���r-���Zclassmanagerr���r���r����_new_classmanager_instance����s����z)InstanceEvents._new_classmanager_instance�sqlalchemy.ormc�����������������C���sl���t�|tj�r|S�t�|tj�r"|jS�||jkr2tjS�t�|t�rht|tj�rNtjS�t�	|�}|r`|S�t
|�S�d�S�r���)r���r����ClassManagerr����MapperZ
class_manager�mapperr���r����manager_of_classrM���)r����ormr����managerr���r���r���r�������s����

zInstanceEvents._accept_withFc�����������	���������sn���|j�|j�}���r�r0����fdd�}|�|�}|jf�d|i|���|rj|�d�D�]}|�|�jdd��qRd�S�)Nc��������������������sB����s|�����}n|�}�r|�j}z��|f|�|�W��S��r<||�_X�d�S�r�����obj�runid)�stater���r2���r���rY����r����raw�restore_load_contextr���r����wrap����s����
z$InstanceEvents._listen.<locals>.wrapr ���T�r ���)r*���r+���r/���r0����subclass_managersr.���)	r���r1���r\���r ���r]���r2���r���r^����mgrr���r[���r���r3�������s����	
zInstanceEvents._listenc��������������������s���t�t|������t����d�S�r���)r4���rK���r5���rM���r6���r7���r���r���r5�������s����zInstanceEvents._clearc�����������������C���s���dS�)a]��Called when the first instance of a particular mapping is called.

This event is called when the ``__init__`` method of a class
        is called the first time for that particular class.    The event
        invokes before ``__init__`` actually proceeds as well as before
        the :meth:`.InstanceEvents.init` event is invoked.

Nr���)r:���rV���r���r���r���r����
first_init����s����zInstanceEvents.first_initc�����������������C���s���dS�)a���Receive an instance when its constructor is called.

This method is only called during a userland construction of
        an object, in conjunction with the object's constructor, e.g.
        its ``__init__`` method.  It is not called when an object is
        loaded from the database; see the :meth:`.InstanceEvents.load`
        event in order to intercept a database load.

The event is called before the actual ``__init__`` constructor
        of the object is called.  The ``kwargs`` dictionary may be
        modified in-place in order to affect what is passed to
        ``__init__``.

:param target: the mapped instance.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :param args: positional arguments passed to the ``__init__`` method.
         This is passed as a tuple and is currently immutable.
        :param kwargs: keyword arguments passed to the ``__init__`` method.
         This structure *can* be altered in place.

.. seealso::

:meth:`.InstanceEvents.init_failure`

:meth:`.InstanceEvents.load`

Nr����r:���r����args�kwargsr���r���r����init����s����zInstanceEvents.initc�����������������C���s���dS�)a���Receive an instance when its constructor has been called,
        and raised an exception.

This method is only called during a userland construction of
        an object, in conjunction with the object's constructor, e.g.
        its ``__init__`` method. It is not called when an object is loaded
        from the database.

The event is invoked after an exception raised by the ``__init__``
        method is caught.  After the event
        is invoked, the original exception is re-raised outwards, so that
        the construction of the object still raises an exception.   The
        actual exception and stack trace raised should be present in
        ``sys.exc_info()``.

:param target: the mapped instance.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :param args: positional arguments that were passed to the ``__init__``
         method.
        :param kwargs: keyword arguments that were passed to the ``__init__``
         method.

.. seealso::

:meth:`.InstanceEvents.init`

:meth:`.InstanceEvents.load`

Nr���rc���r���r���r����init_failure��s����zInstanceEvents.init_failurec�����������������C���s���dS�)a%
��Receive an object instance after it has been created via
        ``__new__``, and after initial attribute population has
        occurred.

This typically occurs when the instance is created based on
        incoming result rows, and is only called once for that
        instance's lifetime.

.. warning::

During a result-row load, this event is invoked when the
            first row received for this instance is processed.  When using
            eager loading with collection-oriented attributes, the additional
            rows that are to be loaded / processed in order to load subsequent
            collection items have not occurred yet.   This has the effect
            both that collections will not be fully loaded, as well as that
            if an operation occurs within this event handler that emits
            another database load operation for the object, the "loading
            context" for the object can change and interfere with the
            existing eager loaders still in progress.

Examples of what can cause the "loading context" to change within
            the event handler include, but are not necessarily limited to:

* accessing deferred attributes that weren't part of the row,
              will trigger an "undefer" operation and refresh the object

* accessing attributes on a joined-inheritance subclass that
              weren't part of the row, will trigger a refresh operation.

As of SQLAlchemy 1.3.14, a warning is emitted when this occurs. The
            :paramref:`.InstanceEvents.restore_load_context` option may  be
            used on the event to prevent this warning; this will ensure that
            the existing loading context is maintained for the object after the
            event is called::

@event.listens_for(
                    SomeClass, "load", restore_load_context=True)
                def on_load(instance, context):
                    instance.some_unloaded_attribute

.. versionchanged:: 1.3.14 Added
               :paramref:`.InstanceEvents.restore_load_context`
               and :paramref:`.SessionEvents.restore_load_context` flags which
               apply to "on load" events, which will ensure that the loading
               context for an object is restored when the event hook is
               complete; a warning is emitted if the load context of the object
               changes without this flag being set.

The :meth:`.InstanceEvents.load` event is also available in a
        class-method decorator format called :func:`_orm.reconstructor`.

:param target: the mapped instance.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :param context: the :class:`.QueryContext` corresponding to the
         current :class:`_query.Query` in progress.  This argument may be
         ``None`` if the load does not correspond to a :class:`_query.Query`,
         such as during :meth:`.Session.merge`.

.. seealso::

:meth:`.InstanceEvents.init`

:meth:`.InstanceEvents.refresh`

:meth:`.SessionEvents.loaded_as_persistent`

:ref:`mapping_constructors`

Nr���)r:���r����contextr���r���r����load>��s����zInstanceEvents.loadc�����������������C���s���dS�)ak��Receive an object instance after one or more attributes have
        been refreshed from a query.

Contrast this to the :meth:`.InstanceEvents.load` method, which
        is invoked when the object is first loaded from a query.

.. note:: This event is invoked within the loader process before
           eager loaders may have been completed, and the object's state may
           not be complete.  Additionally, invoking row-level refresh
           operations on the object will place the object into a new loader
           context, interfering with the existing load context.   See the note
           on :meth:`.InstanceEvents.load` for background on making use of the
           :paramref:`.InstanceEvents.restore_load_context` parameter, in
           order to resolve this scenario.

:param target: the mapped instance.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :param context: the :class:`.QueryContext` corresponding to the
         current :class:`_query.Query` in progress.
        :param attrs: sequence of attribute names which
         were populated, or None if all column-mapped, non-deferred
         attributes were populated.

.. seealso::

:meth:`.InstanceEvents.load`

Nr���)r:���r���rh����attrsr���r���r����refresh���s����zInstanceEvents.refreshc�����������������C���s���dS�)a��Receive an object instance after one or more attributes that
        contain a column-level default or onupdate handler have been refreshed
        during persistence of the object's state.

This event is the same as :meth:`.InstanceEvents.refresh` except
        it is invoked within the unit of work flush process, and includes
        only non-primary-key columns that have column level default or
        onupdate handlers, including Python callables as well as server side
        defaults and triggers which may be fetched via the RETURNING clause.

.. note::

While the :meth:`.InstanceEvents.refresh_flush` event is triggered
            for an object that was INSERTed as well as for an object that was
            UPDATEd, the event is geared primarily  towards the UPDATE process;
            it is mostly an internal artifact that INSERT actions can also
            trigger this event, and note that **primary key columns for an
            INSERTed row are explicitly omitted** from this event.  In order to
            intercept the newly INSERTed state of an object, the
            :meth:`.SessionEvents.pending_to_persistent` and
            :meth:`.MapperEvents.after_insert` are better choices.

.. versionadded:: 1.0.5

:param target: the mapped instance.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :param flush_context: Internal :class:`.UOWTransaction` object
         which handles the details of the flush.
        :param attrs: sequence of attribute names which
         were populated.

.. seealso::

:ref:`orm_server_defaults`

:ref:`metadata_defaults_toplevel`

Nr���)r:���r����
flush_contextrj���r���r���r����
refresh_flush���s����zInstanceEvents.refresh_flushc�����������������C���s���dS�)a��Receive an object instance after its attributes or some subset
        have been expired.

'keys' is a list of attribute names.  If None, the entire
        state was expired.

Nr���)r:���r���rj���r���r���r����expire���s����zInstanceEvents.expirec�����������������C���s���dS�)a���Receive an object instance when its associated state is
        being pickled.

:param target: the mapped instance.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :param state_dict: the dictionary returned by
         :class:`.InstanceState.__getstate__`, containing the state
         to be pickled.

Nr����r:���r���Z
state_dictr���r���r����pickle���s����zInstanceEvents.picklec�����������������C���s���dS�)a���Receive an object instance after its associated state has
        been unpickled.

:param target: the mapped instance.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :param state_dict: the dictionary sent to
         :class:`.InstanceState.__setstate__`, containing the state
         dictionary which was pickled.

Nr���ro���r���r���r����unpickle���s����zInstanceEvents.unpickle)FFF)r?���r@���rA���rB���rC���r���rQ���rD���rE���rO���r����dependenciesr���r3���r5���rb���rf���rg���ri���rk���rm���rn���rp���rq���rF���r���r���r7���r���rK�������s0���/
����!
!K *rK���c�������������������@���sH���e�Zd�ZdZdd��Zedd���ZG�dd��de�Zdd	��Z	ed
d���Z
dS�)
�_EventsHoldz�Hold onto listeners against unmapped, uninstrumented classes.

Establish _listen() for that class' mapper/instrumentation when
    those objects are created for that class.

c�����������������C���s
���||�_�d�S�r���rG���rH���r���r���r���rI���	��s����z_EventsHold.__init__c�����������������C���s���|�j�����d�S�r���)�	all_holds�clearr6���r���r���r���r5�����s����z_EventsHold._clearc�������������������@���s���e�Zd�ZdZeddd��ZdS�)z_EventsHold.HoldEventsNFc�����������������K���s����|j�}|j|jkr |j|j�}ni��}|j|j<�tj�||��||||f||j<�|r�t|j����}|r�|�	d�}	|�
|	�����|�|	�}
|
d�k	rb|�|
�j
f�|d|d�|���qbd�S�)Nr���F�r\���r ����retval)r*���r-���rt���r���r"���Z_stored_in_collection�_key�list�__subclasses__�pop�extend�resolver.���r!���)r���r1���r\���r ���rw���r2���r����
collection�stack�subclass�subjectr���r���r���r3�����s(����

����z_EventsHold.HoldEvents._listen)FFF)r?���r@���rA���rD���rE���r3���r���r���r���r����
HoldEvents��s���������r����c�����������������C���s(���|j�}t|t�r$|j|j�}||j=�d�S�r���)r*���r���rs���rt���r-���rx���)r:���r1���r���r~���r���r���r���r&���.��s����
z_EventsHold.removec�����������	������C���s\���|j�D�]P}||�jkr|�j|�}|���D�].\}}}}|s>||kr&|�|�j|d|d��q&qd�S�)NFrv���)�__mro__rt����valuesr.���r!���)	r���r-���r����r����r~���r1���r\���r ���rw���r���r���r���rN���5��s����

���z_EventsHold.populateN)r?���r@���rA���rB���rI���rE���r5����objectr����r&���rN���r���r���r���r���rs�����s���
rs���c�������������������@���s:���e�Zd�Ze���Zdd��ZG�dd��deje	�Z
e�e
�Z
dS�)rM���c�����������������C���s
���t��|�S�r���)r���rT���rH���r���r���r���r}���I��s����z_InstanceEventsHold.resolvec�������������������@���s���e�Zd�ZdS�)z&_InstanceEventsHold.HoldInstanceEventsN�r?���r@���rA���r���r���r���r����HoldInstanceEventsL��s���r����N)r?���r@���rA���r,����WeakKeyDictionaryrt���r}���rs���r����rK���r����r���rJ���r%���r���r���r���r���rM���F��s���rM���c�����������������������s����e�Zd�ZdZdZejZedd���Z	ee
�d�dd����Zed#d	d
��Z
e��fdd��Zd
d��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd ��Zd!d"��Z���ZS�)$�MapperEventsa�
��Define events specific to mappings.

e.g.::

from sqlalchemy import event

def my_before_insert_listener(mapper, connection, target):
            # execute a stored procedure upon INSERT,
            # apply the value to the row to be inserted
            target.calculated_value = connection.scalar(
                                        "select my_special_function(%d)"
                                        % target.special_number)

# associate the listener function with SomeClass,
        # to execute during the "before_insert" hook
        event.listen(
            SomeClass, 'before_insert', my_before_insert_listener)

Available targets include:

Mapper events provide hooks into critical sections of the
    mapper, including those related to object instrumentation,
    object loading, and object persistence. In particular, the
    persistence methods :meth:`~.MapperEvents.before_insert`,
    and :meth:`~.MapperEvents.before_update` are popular
    places to augment the state being persisted - however, these
    methods operate with several significant restrictions. The
    user is encouraged to evaluate the
    :meth:`.SessionEvents.before_flush` and
    :meth:`.SessionEvents.after_flush` methods as more
    flexible and user-friendly hooks in which to apply
    additional database state during a flush.

When using :class:`.MapperEvents`, several modifiers are
    available to the :func:`.event.listen` function.

:param propagate=False: When True, the event listener should
       be applied to all inheriting mappers and/or the mappers of
       inheriting classes, as well as any
       mapper which is the target of this listener.
    :param raw=False: When True, the "target" argument passed
       to applicable event listener functions will be the
       instance's :class:`.InstanceState` management
       object, rather than the mapped instance itself.
    :param retval=False: when True, the user-defined event function
       must have a return value, the purpose of which is either to
       control subsequent event propagation, or to otherwise alter
       the operation in progress by the mapper.   Possible return
       values are:

* ``sqlalchemy.orm.interfaces.EXT_CONTINUE`` - continue event
         processing normally.
       * ``sqlalchemy.orm.interfaces.EXT_STOP`` - cancel all subsequent
         event handlers in the chain.
       * other values - the return value specified by specific listeners.

rL���c�����������������C���s���t��||��d�S�r���)�_MapperEventsHoldrN���)r���r-���rS���r���r���r����_new_mapper_instance���s����z!MapperEvents._new_mapper_instancerP���c�����������������C���sP���||j�krtjS�t|t�rHt|tj�r*|S�t|�}|d�k	r>|S�t|�S�n|S�d�S�r���)rS���r���rR���r���r���r���r���r����)r���rU���r���rS���r���r���r���r������s����

zMapperEvents._accept_withFc��������������������s����|j�|j|j��}}��|dkr2|tjk	r2t�d���r:�s��s|t|�|�}zt|�d��	d�d��W�n�t
k
rz���d��Y�nX������fdd�}	|�|	�}|r�|jD�]}
|�
|
�jf�dd	i|���q�n|jf�|��d�S�)
N)�before_configured�after_configuredz{'before_configured' and 'after_configured' ORM events only invoke with the mapper() function or Mapper class as the target.r���r���r���c���������������������sF����s$�d�k	r$t�|��}�|������|��<��s8��|�|��tjS���|�|�S�d�S�r���)ry���rX���r���ZEXT_CONTINUE�r���r2����r���r\���rw���Ztarget_indexr���r���r^������s����
z"MapperEvents._listen.<locals>.wrapr ���T)r*���r)���r+���r���rR���r����warnr$���r����index�
ValueErrorr/���Zself_and_descendantsr.���r0���)r���r1���r\���rw���r ���r2���r���r)����methr^���rS���r���r����r���r3������s:�����
���
�

��
zMapperEvents._listenc��������������������s���t�t|������t����d�S�r���)r4���r����r5���r����r6���r7���r���r���r5������s����zMapperEvents._clearc�����������������C���s���dS�)a��Receive a class when the mapper is first constructed,
        before instrumentation is applied to the mapped class.

This event is the earliest phase of mapper construction.
        Most attributes of the mapper are not yet initialized.

This listener can either be applied to the :class:`_orm.Mapper`
        class overall, or to any un-mapped class which serves as a base
        for classes that will be mapped (using the ``propagate=True`` flag)::

Base = declarative_base()

@event.listens_for(Base, "instrument_class", propagate=True)
            def on_new_class(mapper, cls_):
                " ... "

:param mapper: the :class:`_orm.Mapper` which is the target
         of this event.
        :param class\_: the mapped class.

Nr����r:���rS���r-���r���r���r����instrument_class���s����zMapperEvents.instrument_classc�����������������C���s���dS�)a���Called right before a specific mapper is to be configured.

This event is intended to allow a specific mapper to be skipped during
        the configure step, by returning the :attr:`.orm.interfaces.EXT_SKIP`
        symbol which indicates to the :func:`.configure_mappers` call that this
        particular mapper (or hierarchy of mappers, if ``propagate=True`` is
        used) should be skipped in the current configuration run.  When one or
        more mappers are skipped, the he "new mappers" flag will remain set,
        meaning the :func:`.configure_mappers` function will continue to be
        called when mappers are used, to continue to try to configure all
        available mappers.

In comparison to the other configure-level events,
        :meth:`.MapperEvents.before_configured`,
        :meth:`.MapperEvents.after_configured`, and
        :meth:`.MapperEvents.mapper_configured`, the
        :meth;`.MapperEvents.before_mapper_configured` event provides for a
        meaningful return value when it is registered with the ``retval=True``
        parameter.

.. versionadded:: 1.3

e.g.::

from sqlalchemy.orm import EXT_SKIP

Base = declarative_base()

DontConfigureBase = declarative_base()

@event.listens_for(
                DontConfigureBase,
                "before_mapper_configured", retval=True, propagate=True)
            def dont_configure(mapper, cls):
                return EXT_SKIP

.. seealso::

:meth:`.MapperEvents.before_configured`

:meth:`.MapperEvents.after_configured`

:meth:`.MapperEvents.mapper_configured`

Nr���r����r���r���r����before_mapper_configured���s����z%MapperEvents.before_mapper_configuredc�����������������C���s���dS�)a	��Called when a specific mapper has completed its own configuration
        within the scope of the :func:`.configure_mappers` call.

The :meth:`.MapperEvents.mapper_configured` event is invoked
        for each mapper that is encountered when the
        :func:`_orm.configure_mappers` function proceeds through the current
        list of not-yet-configured mappers.
        :func:`_orm.configure_mappers` is typically invoked
        automatically as mappings are first used, as well as each time
        new mappers have been made available and new mapper use is
        detected.

When the event is called, the mapper should be in its final
        state, but **not including backrefs** that may be invoked from
        other mappers; they might still be pending within the
        configuration operation.    Bidirectional relationships that
        are instead configured via the
        :paramref:`.orm.relationship.back_populates` argument
        *will* be fully available, since this style of relationship does not
        rely upon other possibly-not-configured mappers to know that they
        exist.

For an event that is guaranteed to have **all** mappers ready
        to go including backrefs that are defined only on other
        mappings, use the :meth:`.MapperEvents.after_configured`
        event; this event invokes only after all known mappings have been
        fully configured.

The :meth:`.MapperEvents.mapper_configured` event, unlike
        :meth:`.MapperEvents.before_configured` or
        :meth:`.MapperEvents.after_configured`,
        is called for each mapper/class individually, and the mapper is
        passed to the event itself.  It also is called exactly once for
        a particular mapper.  The event is therefore useful for
        configurational steps that benefit from being invoked just once
        on a specific mapper basis, which don't require that "backref"
        configurations are necessarily ready yet.

:param mapper: the :class:`_orm.Mapper` which is the target
         of this event.
        :param class\_: the mapped class.

.. seealso::

:meth:`.MapperEvents.before_configured`

:meth:`.MapperEvents.after_configured`

:meth:`.MapperEvents.before_mapper_configured`

Nr���r����r���r���r����mapper_configured*��s����zMapperEvents.mapper_configuredc�����������������C���s���dS�)a���Called before a series of mappers have been configured.

The :meth:`.MapperEvents.before_configured` event is invoked
        each time the :func:`_orm.configure_mappers` function is
        invoked, before the function has done any of its work.
        :func:`_orm.configure_mappers` is typically invoked
        automatically as mappings are first used, as well as each time
        new mappers have been made available and new mapper use is
        detected.

This event can **only** be applied to the :class:`_orm.Mapper` class
        or :func:`.mapper` function, and not to individual mappings or
        mapped classes.  It is only invoked for all mappings as a whole::

from sqlalchemy.orm import mapper

@event.listens_for(mapper, "before_configured")
            def go():
                # ...

Contrast this event to :meth:`.MapperEvents.after_configured`,
        which is invoked after the series of mappers has been configured,
        as well as :meth:`.MapperEvents.before_mapper_configured`
        and :meth:`.MapperEvents.mapper_configured`, which are both invoked
        on a per-mapper basis.

Theoretically this event is called once per
        application, but is actually called any time new mappers
        are to be affected by a :func:`_orm.configure_mappers`
        call.   If new mappings are constructed after existing ones have
        already been used, this event will likely be called again.  To ensure
        that a particular event is only called once and no further, the
        ``once=True`` argument (new in 0.9.4) can be applied::

from sqlalchemy.orm import mapper

@event.listens_for(mapper, "before_configured", once=True)
            def go():
                # ...

.. versionadded:: 0.9.3

.. seealso::

:meth:`.MapperEvents.before_mapper_configured`

:meth:`.MapperEvents.mapper_configured`

:meth:`.MapperEvents.after_configured`

Nr����r:���r���r���r���r����`��s����zMapperEvents.before_configuredc�����������������C���s���dS�)aq��Called after a series of mappers have been configured.

The :meth:`.MapperEvents.after_configured` event is invoked
        each time the :func:`_orm.configure_mappers` function is
        invoked, after the function has completed its work.
        :func:`_orm.configure_mappers` is typically invoked
        automatically as mappings are first used, as well as each time
        new mappers have been made available and new mapper use is
        detected.

Contrast this event to the :meth:`.MapperEvents.mapper_configured`
        event, which is called on a per-mapper basis while the configuration
        operation proceeds; unlike that event, when this event is invoked,
        all cross-configurations (e.g. backrefs) will also have been made
        available for any mappers that were pending.
        Also contrast to :meth:`.MapperEvents.before_configured`,
        which is invoked before the series of mappers has been configured.

from sqlalchemy.orm import mapper

@event.listens_for(mapper, "after_configured")
            def go():
                # ...

Theoretically this event is called once per
        application, but is actually called any time new mappers
        have been affected by a :func:`_orm.configure_mappers`
        call.   If new mappings are constructed after existing ones have
        already been used, this event will likely be called again.  To ensure
        that a particular event is only called once and no further, the
        ``once=True`` argument (new in 0.9.4) can be applied::

from sqlalchemy.orm import mapper

@event.listens_for(mapper, "after_configured", once=True)
            def go():
                # ...

.. seealso::

:meth:`.MapperEvents.before_mapper_configured`

:meth:`.MapperEvents.mapper_configured`

:meth:`.MapperEvents.before_configured`

Nr���r����r���r���r���r�������s����zMapperEvents.after_configuredc�����������������C���s���dS�)a���Receive an object instance before an INSERT statement
        is emitted corresponding to that instance.

This event is used to modify local, non-object related
        attributes on the instance before an INSERT occurs, as well
        as to emit additional SQL statements on the given
        connection.

The event is often called for a batch of objects of the
        same class before their INSERT statements are emitted at
        once in a later step. In the extremely rare case that
        this is not desirable, the :func:`.mapper` can be
        configured with ``batch=False``, which will cause
        batches of instances to be broken up into individual
        (and more poorly performing) event->persist->event
        steps.

.. warning::

Mapper-level flush events only allow **very limited operations**,
            on attributes local to the row being operated upon only,
            as well as allowing any SQL to be emitted on the given
            :class:`_engine.Connection`.  **Please read fully** the notes
            at :ref:`session_persistence_mapper` for guidelines on using
            these methods; generally, the :meth:`.SessionEvents.before_flush`
            method should be preferred for general on-flush changes.

:param mapper: the :class:`_orm.Mapper` which is the target
         of this event.
        :param connection: the :class:`_engine.Connection` being used to
         emit INSERT statements for this instance.  This
         provides a handle into the current transaction on the
         target database specific to this instance.
        :param target: the mapped instance being persisted.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :return: No return value is supported by this event.

.. seealso::

:ref:`session_persistence_events`

Nr����r:���rS����
connectionr���r���r���r����
before_insert���s����zMapperEvents.before_insertc�����������������C���s���dS�)a���Receive an object instance after an INSERT statement
        is emitted corresponding to that instance.

This event is used to modify in-Python-only
        state on the instance after an INSERT occurs, as well
        as to emit additional SQL statements on the given
        connection.

The event is often called for a batch of objects of the
        same class after their INSERT statements have been
        emitted at once in a previous step. In the extremely
        rare case that this is not desirable, the
        :func:`.mapper` can be configured with ``batch=False``,
        which will cause batches of instances to be broken up
        into individual (and more poorly performing)
        event->persist->event steps.

.. warning::

.. seealso::

:ref:`session_persistence_events`

Nr���r����r���r���r����after_insert���s����zMapperEvents.after_insertc�����������������C���s���dS�)a���Receive an object instance before an UPDATE statement
        is emitted corresponding to that instance.

This event is used to modify local, non-object related
        attributes on the instance before an UPDATE occurs, as well
        as to emit additional SQL statements on the given
        connection.

This method is called for all instances that are
        marked as "dirty", *even those which have no net changes
        to their column-based attributes*. An object is marked
        as dirty when any of its column-based attributes have a
        "set attribute" operation called or when any of its
        collections are modified. If, at update time, no
        column-based attributes have any net changes, no UPDATE
        statement will be issued. This means that an instance
        being sent to :meth:`~.MapperEvents.before_update` is
        *not* a guarantee that an UPDATE statement will be
        issued, although you can affect the outcome here by
        modifying attributes so that a net change in value does
        exist.

To detect if the column-based attributes on the object have net
        changes, and will therefore generate an UPDATE statement, use
        ``object_session(instance).is_modified(instance,
        include_collections=False)``.

The event is often called for a batch of objects of the
        same class before their UPDATE statements are emitted at
        once in a later step. In the extremely rare case that
        this is not desirable, the :func:`.mapper` can be
        configured with ``batch=False``, which will cause
        batches of instances to be broken up into individual
        (and more poorly performing) event->persist->event
        steps.

.. warning::

:param mapper: the :class:`_orm.Mapper` which is the target
         of this event.
        :param connection: the :class:`_engine.Connection` being used to
         emit UPDATE statements for this instance.  This
         provides a handle into the current transaction on the
         target database specific to this instance.
        :param target: the mapped instance being persisted.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :return: No return value is supported by this event.

.. seealso::

:ref:`session_persistence_events`

Nr���r����r���r���r����
before_update(��s����zMapperEvents.before_updatec�����������������C���s���dS�)ad��Receive an object instance after an UPDATE statement
        is emitted corresponding to that instance.

This event is used to modify in-Python-only
        state on the instance after an UPDATE occurs, as well
        as to emit additional SQL statements on the given
        connection.

This method is called for all instances that are
        marked as "dirty", *even those which have no net changes
        to their column-based attributes*, and for which
        no UPDATE statement has proceeded. An object is marked
        as dirty when any of its column-based attributes have a
        "set attribute" operation called or when any of its
        collections are modified. If, at update time, no
        column-based attributes have any net changes, no UPDATE
        statement will be issued. This means that an instance
        being sent to :meth:`~.MapperEvents.after_update` is
        *not* a guarantee that an UPDATE statement has been
        issued.

To detect if the column-based attributes on the object have net
        changes, and therefore resulted in an UPDATE statement, use
        ``object_session(instance).is_modified(instance,
        include_collections=False)``.

The event is often called for a batch of objects of the
        same class after their UPDATE statements have been emitted at
        once in a previous step. In the extremely rare case that
        this is not desirable, the :func:`.mapper` can be
        configured with ``batch=False``, which will cause
        batches of instances to be broken up into individual
        (and more poorly performing) event->persist->event
        steps.

.. warning::

.. seealso::

:ref:`session_persistence_events`

Nr���r����r���r���r����after_updatei��s����zMapperEvents.after_updatec�����������������C���s���dS�)a���Receive an object instance before a DELETE statement
        is emitted corresponding to that instance.

This event is used to emit additional SQL statements on
        the given connection as well as to perform application
        specific bookkeeping related to a deletion event.

The event is often called for a batch of objects of the
        same class before their DELETE statements are emitted at
        once in a later step.

.. warning::

:param mapper: the :class:`_orm.Mapper` which is the target
         of this event.
        :param connection: the :class:`_engine.Connection` being used to
         emit DELETE statements for this instance.  This
         provides a handle into the current transaction on the
         target database specific to this instance.
        :param target: the mapped instance being deleted.  If
         the event is configured with ``raw=True``, this will
         instead be the :class:`.InstanceState` state-management
         object associated with the instance.
        :return: No return value is supported by this event.

.. seealso::

:ref:`session_persistence_events`

Nr���r����r���r���r����
before_delete���s����zMapperEvents.before_deletec�����������������C���s���dS�)a���Receive an object instance after a DELETE statement
        has been emitted corresponding to that instance.

This event is used to emit additional SQL statements on
        the given connection as well as to perform application
        specific bookkeeping related to a deletion event.

The event is often called for a batch of objects of the
        same class after their DELETE statements have been emitted at
        once in a previous step.

.. warning::

.. seealso::

:ref:`session_persistence_events`

Nr���r����r���r���r����after_delete���s����zMapperEvents.after_delete)FFF)r?���r@���rA���rB���rC���r���rR���rD���rE���r����r���rr���r���r3���r5���r����r����r����r����r����r����r����r����r����r����r����rF���r���r���r7���r���r����R��s4���A
������10675..A@(r����c�������������������@���s:���e�Zd�Ze���Zdd��ZG�dd��deje	�Z
e�e
�Z
dS�)r����c�����������������C���s���t�|�S�r���r���rH���r���r���r���r}������s����z_MapperEventsHold.resolvec�������������������@���s���e�Zd�ZdS�)z"_MapperEventsHold.HoldMapperEventsNr����r���r���r���r����HoldMapperEvents���s���r����N)r?���r@���rA���r,���r����rt���r}���rs���r����r����r����r���rJ���r%���r���r���r���r���r�������s���r����c�������������������@���s^��e�Zd�ZdZdZeZdd��Zedd���Z	edCdd	��Z
d
d��Zdd
��Zdd��Z
dd��Zdd��Zdd��Zdd��Zdd��Zdd��Zdd��Zedd���Zed d!���Ze�d"d#d$d%d&gd'd(���d)d*���Ze�d"d#d$d%d&gd+d(���d,d-���Zed.d/���Zed0d1���Zed2d3���Zed4d5���Zed6d7���Zed8d9���Z ed:d;���Z!ed<d=���Z"ed>d?���Z#ed@dA���Z$dBS�)D�
SessionEventsar��Define events specific to :class:`.Session` lifecycle.

e.g.::

from sqlalchemy import event
        from sqlalchemy.orm import sessionmaker

def my_before_commit(session):
            print("before commit!")

Session = sessionmaker()

event.listen(Session, "before_commit", my_before_commit)

The :func:`~.event.listen` function will accept
    :class:`.Session` objects as well as the return result
    of :class:`~.sessionmaker()` and :class:`~.scoped_session()`.

Additionally, it accepts the :class:`.Session` class which
    will apply listeners to all :class:`.Session` instances
    globally.

:param raw=False: When True, the "target" argument passed
       to applicable event listener functions that work on individual
       objects will be the instance's :class:`.InstanceState` management
       object, rather than the mapped instance itself.

.. versionadded:: 1.3.14

:param restore_load_context=False: Applies to the
       :meth:`.SessionEvents.loaded_as_persistent` event.  Restores the loader
       context of the object when the event hook is complete, so that ongoing
       eager load operations continue to target the object appropriately.  A
       warning is emitted if the object is moved to a new loader context from
       within this event if this flag is not set.

.. versionadded:: 1.3.14

ZSomeSessionOrFactoryc�����������������C���s���t��|�j��|�S�r���)�$_sessionevents_lifecycle_event_names�addr?����r���r���r���r����_lifecycle_event6��s����zSessionEvents._lifecycle_eventc�����������������C���s����t�|t�r8|j}t�|t�s8t�|t�r.t|t�s8t�d��t�|t�rH|j	S�t�|t�rpt|t�r`tS�t|t�r�|S�nt�|t�r~|S�d�S�d�S�)NzrSession event listen on a scoped_session requires that its creation callable is associated with the Session class.)
r���r
���Zsession_factoryr���r���r���r���r����
ArgumentErrorr-���r���r���r���r���r���:��s(����

���

zSessionEvents._accept_withFc��������������������sF���|j�tk}|r6�r�r6|j������fdd�}|�|�}|jf�|��d�S�)Nc��������������������sP����s|����}|d�krd�S�n|}�r(|j}z��|�|f|�|�W��S��rJ||_X�d�S�r���rW���)�sessionrZ���r���r2���r���rY���r[���r���r���r^���_��s����z#SessionEvents._listen.<locals>.wrap)r)���r����r+���r/���r0���)r���r1���r\���r]���r2���Zis_instance_eventr^���r���r[���r���r3���T��s�����
zSessionEvents._listenc�����������������C���s���dS�)aq��Execute when a new :class:`.SessionTransaction` is created.

This event differs from :meth:`~.SessionEvents.after_begin`
        in that it occurs for each :class:`.SessionTransaction`
        overall, as opposed to when transactions are begun
        on individual database connections.  It is also invoked
        for nested transactions and subtransactions, and is always
        matched by a corresponding
        :meth:`~.SessionEvents.after_transaction_end` event
        (assuming normal operation of the :class:`.Session`).

:param session: the target :class:`.Session`.
        :param transaction: the target :class:`.SessionTransaction`.

To detect if this is the outermost
         :class:`.SessionTransaction`, as opposed to a "subtransaction" or a
         SAVEPOINT, test that the :attr:`.SessionTransaction.parent` attribute
         is ``None``::

@event.listens_for(session, "after_transaction_create")
                def after_transaction_create(session, transaction):
                    if transaction.parent is None:
                        # work with top-level transaction

To detect if the :class:`.SessionTransaction` is a SAVEPOINT, use the
         :attr:`.SessionTransaction.nested` attribute::

@event.listens_for(session, "after_transaction_create")
                def after_transaction_create(session, transaction):
                    if transaction.nested:
                        # work with SAVEPOINT transaction

.. seealso::

:class:`.SessionTransaction`

:meth:`~.SessionEvents.after_transaction_end`

Nr����r:���r�����transactionr���r���r����after_transaction_createt��s����z&SessionEvents.after_transaction_createc�����������������C���s���dS�)a���Execute when the span of a :class:`.SessionTransaction` ends.

This event differs from :meth:`~.SessionEvents.after_commit`
        in that it corresponds to all :class:`.SessionTransaction`
        objects in use, including those for nested transactions
        and subtransactions, and is always matched by a corresponding
        :meth:`~.SessionEvents.after_transaction_create` event.

:param session: the target :class:`.Session`.
        :param transaction: the target :class:`.SessionTransaction`.

@event.listens_for(session, "after_transaction_create")
                def after_transaction_end(session, transaction):
                    if transaction.parent is None:
                        # work with top-level transaction

To detect if the :class:`.SessionTransaction` is a SAVEPOINT, use the
         :attr:`.SessionTransaction.nested` attribute::

@event.listens_for(session, "after_transaction_create")
                def after_transaction_end(session, transaction):
                    if transaction.nested:
                        # work with SAVEPOINT transaction

.. seealso::

:class:`.SessionTransaction`

:meth:`~.SessionEvents.after_transaction_create`

Nr���r����r���r���r����after_transaction_end���s����z#SessionEvents.after_transaction_endc�����������������C���s���dS�)a!��Execute before commit is called.

.. note::

The :meth:`~.SessionEvents.before_commit` hook is *not* per-flush,
            that is, the :class:`.Session` can emit SQL to the database
            many times within the scope of a transaction.
            For interception of these events, use the
            :meth:`~.SessionEvents.before_flush`,
            :meth:`~.SessionEvents.after_flush`, or
            :meth:`~.SessionEvents.after_flush_postexec`
            events.

:param session: The target :class:`.Session`.

.. seealso::

:meth:`~.SessionEvents.after_commit`

:meth:`~.SessionEvents.after_begin`

:meth:`~.SessionEvents.after_transaction_create`

:meth:`~.SessionEvents.after_transaction_end`

Nr����r:���r����r���r���r����
before_commit���s����zSessionEvents.before_commitc�����������������C���s���dS�)aq��Execute after a commit has occurred.

.. note::

The :meth:`~.SessionEvents.after_commit` hook is *not* per-flush,
            that is, the :class:`.Session` can emit SQL to the database
            many times within the scope of a transaction.
            For interception of these events, use the
            :meth:`~.SessionEvents.before_flush`,
            :meth:`~.SessionEvents.after_flush`, or
            :meth:`~.SessionEvents.after_flush_postexec`
            events.

.. note::

The :class:`.Session` is not in an active transaction
            when the :meth:`~.SessionEvents.after_commit` event is invoked,
            and therefore can not emit SQL.  To emit SQL corresponding to
            every transaction, use the :meth:`~.SessionEvents.before_commit`
            event.

:param session: The target :class:`.Session`.

.. seealso::

:meth:`~.SessionEvents.before_commit`

:meth:`~.SessionEvents.after_begin`

:meth:`~.SessionEvents.after_transaction_create`

:meth:`~.SessionEvents.after_transaction_end`

Nr���r����r���r���r����after_commit���s����zSessionEvents.after_commitc�����������������C���s���dS�)a���Execute after a real DBAPI rollback has occurred.

Note that this event only fires when the *actual* rollback against
        the database occurs - it does *not* fire each time the
        :meth:`.Session.rollback` method is called, if the underlying
        DBAPI transaction has already been rolled back.  In many
        cases, the :class:`.Session` will not be in
        an "active" state during this event, as the current
        transaction is not valid.   To acquire a :class:`.Session`
        which is active after the outermost rollback has proceeded,
        use the :meth:`.SessionEvents.after_soft_rollback` event, checking the
        :attr:`.Session.is_active` flag.

:param session: The target :class:`.Session`.

Nr���r����r���r���r����after_rollback��s����zSessionEvents.after_rollbackc�����������������C���s���dS�)az��Execute after any rollback has occurred, including "soft"
        rollbacks that don't actually emit at the DBAPI level.

This corresponds to both nested and outer rollbacks, i.e.
        the innermost rollback that calls the DBAPI's
        rollback() method, as well as the enclosing rollback
        calls that only pop themselves from the transaction stack.

The given :class:`.Session` can be used to invoke SQL and
        :meth:`.Session.query` operations after an outermost rollback
        by first checking the :attr:`.Session.is_active` flag::

@event.listens_for(Session, "after_soft_rollback")
            def do_something(session, previous_transaction):
                if session.is_active:
                    session.execute("select * from some_table")

:param session: The target :class:`.Session`.
        :param previous_transaction: The :class:`.SessionTransaction`
         transactional marker object which was just closed.   The current
         :class:`.SessionTransaction` for the given :class:`.Session` is
         available via the :attr:`.Session.transaction` attribute.

Nr���)r:���r����Zprevious_transactionr���r���r����after_soft_rollback��s����z!SessionEvents.after_soft_rollbackc�����������������C���s���dS�)aL��Execute before flush process has started.

:param session: The target :class:`.Session`.
        :param flush_context: Internal :class:`.UOWTransaction` object
         which handles the details of the flush.
        :param instances: Usually ``None``, this is the collection of
         objects which can be passed to the :meth:`.Session.flush` method
         (note this usage is deprecated).

.. seealso::

:meth:`~.SessionEvents.after_flush`

:meth:`~.SessionEvents.after_flush_postexec`

:ref:`session_persistence_events`

Nr���)r:���r����rl���Z	instancesr���r���r����before_flush1��s����zSessionEvents.before_flushc�����������������C���s���dS�)a���Execute after flush has completed, but before commit has been
        called.

Note that the session's state is still in pre-flush, i.e. 'new',
        'dirty', and 'deleted' lists still show pre-flush state as well
        as the history settings on instance attributes.

.. warning:: This event runs after the :class:`.Session` has emitted
           SQL to modify the database, but **before** it has altered its
           internal state to reflect those changes, including that newly
           inserted objects are placed into the identity map.  ORM operations
           emitted within this event such as loads of related items
           may produce new identity map entries that will immediately
           be replaced, sometimes causing confusing results.  SQLAlchemy will
           emit a warning for this condition as of version 1.3.9.

:param session: The target :class:`.Session`.
        :param flush_context: Internal :class:`.UOWTransaction` object
         which handles the details of the flush.

.. seealso::

:meth:`~.SessionEvents.before_flush`

:meth:`~.SessionEvents.after_flush_postexec`

:ref:`session_persistence_events`

Nr����r:���r����rl���r���r���r����after_flushE��s����zSessionEvents.after_flushc�����������������C���s���dS�)a���Execute after flush has completed, and after the post-exec
        state occurs.

This will be when the 'new', 'dirty', and 'deleted' lists are in
        their final state.  An actual commit() may or may not have
        occurred, depending on whether or not the flush started its own
        transaction or participated in a larger transaction.

:param session: The target :class:`.Session`.
        :param flush_context: Internal :class:`.UOWTransaction` object
         which handles the details of the flush.

.. seealso::

:meth:`~.SessionEvents.before_flush`

:meth:`~.SessionEvents.after_flush`

:ref:`session_persistence_events`

Nr���r����r���r���r����after_flush_postexecd��s����z"SessionEvents.after_flush_postexecc�����������������C���s���dS�)a��Execute after a transaction is begun on a connection

:param session: The target :class:`.Session`.
        :param transaction: The :class:`.SessionTransaction`.
        :param connection: The :class:`_engine.Connection` object
         which will be used for SQL statements.

.. seealso::

:meth:`~.SessionEvents.before_commit`

:meth:`~.SessionEvents.after_commit`

:meth:`~.SessionEvents.after_transaction_create`

:meth:`~.SessionEvents.after_transaction_end`

Nr���)r:���r����r����r����r���r���r����after_begin|��s����zSessionEvents.after_beginc�����������������C���s���dS�)a��Execute before an instance is attached to a session.

This is called before an add, delete or merge causes
        the object to be part of the session.

.. seealso::

:meth:`~.SessionEvents.after_attach`

:ref:`session_lifecycle_events`

Nr����r:���r�����instancer���r���r����
before_attach���s����zSessionEvents.before_attachc�����������������C���s���dS�)a���Execute after an instance is attached to a session.

This is called after an add, delete or merge.

.. note::

As of 0.8, this event fires off *after* the item
           has been fully associated with the session, which is
           different than previous releases.  For event
           handlers that require the object not yet
           be part of session state (such as handlers which
           may autoflush while the target object is not
           yet complete) consider the
           new :meth:`.before_attach` event.

.. seealso::

:meth:`~.SessionEvents.before_attach`

:ref:`session_lifecycle_events`

Nr���r����r���r���r����after_attach���s����zSessionEvents.after_attachz0.9r�����queryZ
query_context�resultc�����������������C���s���|�j�|�j|�j|�jfS�r����r����r����rh���r����)�update_contextr���r���r����<lambda>���s
�����zSessionEvents.<lambda>c�����������������C���s���dS�)a���Execute after a bulk update operation to the session.

This is called as a result of the :meth:`_query.Query.update` method.

:param update_context: an "update context" object which contains
         details about the update, including these attributes:

* ``session`` - the :class:`.Session` involved
            * ``query`` -the :class:`_query.Query`
              object that this update operation
              was called upon.
            * ``values`` The "values" dictionary that was passed to
              :meth:`_query.Query.update`.
            * ``context`` The :class:`.QueryContext` object, corresponding
              to the invocation of an ORM query.
            * ``result`` the :class:`_engine.ResultProxy`
              returned as a result of the
              bulk UPDATE operation.

.. seealso::

:meth:`.QueryEvents.before_compile_update`

:meth:`.SessionEvents.after_bulk_delete`

Nr���)r:���r����r���r���r����after_bulk_update���s����zSessionEvents.after_bulk_updatec�����������������C���s���|�j�|�j|�j|�jfS�r���r����)�delete_contextr���r���r���r�������s
�����c�����������������C���s���dS�)a]��Execute after a bulk delete operation to the session.

This is called as a result of the :meth:`_query.Query.delete` method.

:param delete_context: a "delete context" object which contains
         details about the update, including these attributes:

* ``session`` - the :class:`.Session` involved
            * ``query`` -the :class:`_query.Query`
              object that this update operation
              was called upon.
            * ``context`` The :class:`.QueryContext` object, corresponding
              to the invocation of an ORM query.
            * ``result`` the :class:`_engine.ResultProxy`
              returned as a result of the
              bulk DELETE operation.

.. seealso::

:meth:`.QueryEvents.before_compile_delete`

:meth:`.SessionEvents.after_bulk_update`

Nr���)r:���r����r���r���r����after_bulk_delete���s����zSessionEvents.after_bulk_deletec�����������������C���s���dS�)a��Intercept the "transient to pending" transition for a specific object.

:param session: target :class:`.Session`

:param instance: the ORM-mapped instance being operated upon.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����transient_to_pending��s����z"SessionEvents.transient_to_pendingc�����������������C���s���dS�)aG��Intercept the "pending to transient" transition for a specific object.

This less common transition occurs when an pending object that has
        not been flushed is evicted from the session; this can occur
        when the :meth:`.Session.rollback` method rolls back the transaction,
        or when the :meth:`.Session.expunge` method is used.

:param session: target :class:`.Session`

:param instance: the ORM-mapped instance being operated upon.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����pending_to_transient��s����z"SessionEvents.pending_to_transientc�����������������C���s���dS�)a
��Intercept the "persistent to transient" transition for a specific object.

This less common transition occurs when an pending object that has
        has been flushed is evicted from the session; this can occur
        when the :meth:`.Session.rollback` method rolls back the transaction.

:param session: target :class:`.Session`

:param instance: the ORM-mapped instance being operated upon.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����persistent_to_transient,��s����z%SessionEvents.persistent_to_transientc�����������������C���s���dS�)ae��Intercept the "pending to persistent"" transition for a specific object.

This event is invoked within the flush process, and is
        similar to scanning the :attr:`.Session.new` collection within
        the :meth:`.SessionEvents.after_flush` event.  However, in this
        case the object has already been moved to the persistent state
        when the event is called.

:param session: target :class:`.Session`

:param instance: the ORM-mapped instance being operated upon.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����pending_to_persistent@��s����z#SessionEvents.pending_to_persistentc�����������������C���s���dS�)aQ��Intercept the "detached to persistent" transition for a specific object.

This event is a specialization of the
        :meth:`.SessionEvents.after_attach` event which is only invoked
        for this specific transition.  It is invoked typically during the
        :meth:`.Session.add` call, as well as during the
        :meth:`.Session.delete` call if the object was not previously
        associated with the
        :class:`.Session` (note that an object marked as "deleted" remains
        in the "persistent" state until the flush proceeds).

.. note::

If the object becomes persistent as part of a call to
            :meth:`.Session.delete`, the object is **not** yet marked as
            deleted when this event is called.  To detect deleted objects,
            check the ``deleted`` flag sent to the
            :meth:`.SessionEvents.persistent_to_detached` to event after the
            flush proceeds, or check the :attr:`.Session.deleted` collection
            within the :meth:`.SessionEvents.before_flush` event if deleted
            objects need to be intercepted before the flush.

:param session: target :class:`.Session`

:param instance: the ORM-mapped instance being operated upon.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����detached_to_persistentV��s����z$SessionEvents.detached_to_persistentc�����������������C���s���dS�)a���Intercept the "loaded as persistent" transition for a specific object.

This event is invoked within the ORM loading process, and is invoked
        very similarly to the :meth:`.InstanceEvents.load` event.  However,
        the event here is linkable to a :class:`.Session` class or instance,
        rather than to a mapper or class hierarchy, and integrates
        with the other session lifecycle events smoothly.  The object
        is guaranteed to be present in the session's identity map when
        this event is called.

.. note:: This event is invoked within the loader process before
           eager loaders may have been completed, and the object's state may
           not be complete.  Additionally, invoking row-level refresh
           operations on the object will place the object into a new loader
           context, interfering with the existing load context.   See the note
           on :meth:`.InstanceEvents.load` for background on making use of the
           :paramref:`.SessionEvents.restore_load_context` parameter, which
           works in the same manner as that of
           :paramref:`.InstanceEvents.restore_load_context`, in  order to
           resolve this scenario.

:param session: target :class:`.Session`

:param instance: the ORM-mapped instance being operated upon.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����loaded_as_persistentz��s����z"SessionEvents.loaded_as_persistentc�����������������C���s���dS�)a���Intercept the "persistent to deleted" transition for a specific object.

This event is invoked when a persistent object's identity
        is deleted from the database within a flush, however the object
        still remains associated with the :class:`.Session` until the
        transaction completes.

If the transaction is rolled back, the object moves again
        to the persistent state, and the
        :meth:`.SessionEvents.deleted_to_persistent` event is called.
        If the transaction is committed, the object becomes detached,
        which will emit the :meth:`.SessionEvents.deleted_to_detached`
        event.

Note that while the :meth:`.Session.delete` method is the primary
        public interface to mark an object as deleted, many objects
        get deleted due to cascade rules, which are not always determined
        until flush time.  Therefore, there's no way to catch
        every object that will be deleted until the flush has proceeded.
        the :meth:`.SessionEvents.persistent_to_deleted` event is therefore
        invoked at the end of a flush.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����persistent_to_deleted���s����z#SessionEvents.persistent_to_deletedc�����������������C���s���dS�)a���Intercept the "deleted to persistent" transition for a specific object.

This transition occurs only when an object that's been deleted
        successfully in a flush is restored due to a call to
        :meth:`.Session.rollback`.   The event is not called under
        any other circumstances.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����deleted_to_persistent���s����z#SessionEvents.deleted_to_persistentc�����������������C���s���dS�)a���Intercept the "deleted to detached" transition for a specific object.

This event is invoked when a deleted object is evicted
        from the session.   The typical case when this occurs is when
        the transaction for a :class:`.Session` in which the object
        was deleted is committed; the object moves from the deleted
        state to the detached state.

It is also invoked for objects that were deleted in a flush
        when the :meth:`.Session.expunge_all` or :meth:`.Session.close`
        events are called, as well as if the object is individually
        expunged from its deleted state via :meth:`.Session.expunge`.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����deleted_to_detached���s����z!SessionEvents.deleted_to_detachedc�����������������C���s���dS�)a[��Intercept the "persistent to detached" transition for a specific object.

This event is invoked when a persistent object is evicted
        from the session.  There are many conditions that cause this
        to happen, including:

* using a method such as :meth:`.Session.expunge`
          or :meth:`.Session.close`

* Calling the :meth:`.Session.rollback` method, when the object
          was part of an INSERT statement for that session's transaction

:param session: target :class:`.Session`

:param instance: the ORM-mapped instance being operated upon.

:param deleted: boolean.  If True, indicates this object moved
         to the detached state because it was marked as deleted and flushed.

.. versionadded:: 1.1

.. seealso::

:ref:`session_lifecycle_events`

Nr���r����r���r���r����persistent_to_detached���s����z$SessionEvents.persistent_to_detachedN)FF)%r?���r@���rA���rB���rC���r���rD���r����rE���r���r3���r����r����r����r����r����r����r����r����r����r����r����r����r���Z_legacy_signaturer����r����r����r����r����r����r����r����r����r����r����r����r���r���r���r���r����	��sl���(
*'$

�

#
"

r����c�������������������@���s~���e�Zd�ZdZdZeZedd���Ze	dd���Z
e	ddd	��Zd
d��Zdd
��Z
dd��Zdd��Zdd��Zdd��Zdd��Zdd��ZdS�)�AttributeEventsa~
��Define events for object attributes.

These are typically defined on the class-bound descriptor for the
    target class.

e.g.::

from sqlalchemy import event

@event.listens_for(MyClass.collection, 'append', propagate=True)
        def my_append_listener(target, value, initiator):
            print("received append event for target: %s" % target)

Listeners have the option to return a possibly modified version of the
    value, when the :paramref:`.AttributeEvents.retval` flag is passed to
    :func:`.event.listen` or :func:`.event.listens_for`::

def validate_phone(target, value, oldvalue, initiator):
            "Strip non-numeric characters from a phone number"

return re.sub(r'\D', '', value)

# setup listener on UserContact.phone attribute, instructing
        # it to use the return value
        listen(UserContact.phone, 'set', validate_phone, retval=True)

A validation function like the above can also raise an exception
    such as :exc:`ValueError` to halt the operation.

The :paramref:`.AttributeEvents.propagate` flag is also important when
    applying listeners to mapped classes that also have mapped subclasses,
    as when using mapper inheritance patterns::

@event.listens_for(MySuperClass.attr, 'set', propagate=True)
        def receive_set(target, value, initiator):
            print("value set: %s" % target)

The full list of modifiers available to the :func:`.event.listen`
    and :func:`.event.listens_for` functions are below.

:param active_history=False: When True, indicates that the
      "set" event would like to receive the "old" value being
      replaced unconditionally, even if this requires firing off
      database loads. Note that ``active_history`` can also be
      set directly via :func:`.column_property` and
      :func:`_orm.relationship`.

:param propagate=False: When True, the listener function will
      be established not just for the class attribute given, but
      for attributes of the same name on all current subclasses
      of that class, as well as all future subclasses of that
      class, using an additional listener that listens for
      instrumentation events.
    :param raw=False: When True, the "target" argument to the
      event will be the :class:`.InstanceState` management
      object, rather than the mapped instance itself.
    :param retval=False: when True, the user-defined event
      listening must return the "value" argument from the
      function.  This gives the listening function the opportunity
      to change the value that is ultimately used for a "set"
      or "append" event.

zSomeClass.some_attributec�����������������C���s���t�j�|�|�}d|_|S�)NF)r����Events�
_set_dispatch�_active_history)r���Zdispatch_clsr%���r���r���r���r����K��s����zAttributeEvents._set_dispatchc�����������������C���s$���t�|tj�rt|jj|j�S�|S�d�S�r���)r���r���ZMapperPropertyr$����parentr-���r(���r���r���r���r���r���Q��s����zAttributeEvents._accept_withFc�����������
���������s����|j�|j�}��|rd|j_�r"�s<����fdd�}|�|�}|j|d��|r�t�|j�}|�	d�D�].}	|�
|	|j��jdd��|rbd|	|j�j_qbd�S�)NTc��������������������sF����s|�����}��s4|r|d�}nd�}��|�f|����|S���|�f|���S�d�S��Nr���)rX���)r���r����value�r���r\���rw���r���r���r^���j��s����
z%AttributeEvents._listen.<locals>.wrapr_���)r*���r+���r%���r����r/���r0���r���rT���r-���r`���r.���r(���)
r���r1���Zactive_historyr\���rw���r ���r���r^���rV���ra���r���r����r���r3���Y��s����

�zAttributeEvents._listenc�����������������C���s���dS�)a��Receive a collection append event.

The append event is invoked for each element as it is appended
        to the collection.  This occurs for single-item appends as well
        as for a "bulk replace" operation.

:param target: the object instance receiving the event.
          If the listener is registered with ``raw=True``, this will
          be the :class:`.InstanceState` object.
        :param value: the value being appended.  If this listener
          is registered with ``retval=True``, the listener
          function must return this value, or a new value which
          replaces it.
        :param initiator: An instance of :class:`.attributes.Event`
          representing the initiation of the event.  May be modified
          from its original value by backref handlers in order to control
          chained event propagation, as well as be inspected for information
          about the source of the event.
        :return: if the event was registered with ``retval=True``,
         the given value, or a new effective value, should be returned.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

:meth:`.AttributeEvents.bulk_replace`

Nr����r:���r���r�����	initiatorr���r���r����append���s����zAttributeEvents.appendc�����������������C���s���dS�)a	��Receive a collection 'bulk replace' event.

This event is invoked for a sequence of values as they are incoming
        to a bulk collection set operation, which can be
        modified in place before the values are treated as ORM objects.
        This is an "early hook" that runs before the bulk replace routine
        attempts to reconcile which objects are already present in the
        collection and which are being removed by the net replace operation.

It is typical that this method be combined with use of the
        :meth:`.AttributeEvents.append` event.    When using both of these
        events, note that a bulk replace operation will invoke
        the :meth:`.AttributeEvents.append` event for all new items,
        even after :meth:`.AttributeEvents.bulk_replace` has been invoked
        for the collection as a whole.  In order to determine if an
        :meth:`.AttributeEvents.append` event is part of a bulk replace,
        use the symbol :attr:`~.attributes.OP_BULK_REPLACE` to test the
        incoming initiator::

from sqlalchemy.orm.attributes import OP_BULK_REPLACE

@event.listens_for(SomeObject.collection, "bulk_replace")
            def process_collection(target, values, initiator):
                values[:] = [_make_value(value) for value in values]

@event.listens_for(SomeObject.collection, "append", retval=True)
            def process_collection(target, value, initiator):
                # make sure bulk_replace didn't already do it
                if initiator is None or initiator.op is not OP_BULK_REPLACE:
                    return _make_value(value)
                else:
                    return value

.. versionadded:: 1.2

:param target: the object instance receiving the event.
          If the listener is registered with ``raw=True``, this will
          be the :class:`.InstanceState` object.
        :param value: a sequence (e.g. a list) of the values being set.  The
          handler can modify this list in place.
        :param initiator: An instance of :class:`.attributes.Event`
          representing the initiation of the event.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

Nr���)r:���r���r����r����r���r���r����bulk_replace���s����zAttributeEvents.bulk_replacec�����������������C���s���dS�)a���Receive a collection remove event.

:param target: the object instance receiving the event.
          If the listener is registered with ``raw=True``, this will
          be the :class:`.InstanceState` object.
        :param value: the value being removed.
        :param initiator: An instance of :class:`.attributes.Event`
          representing the initiation of the event.  May be modified
          from its original value by backref handlers in order to control
          chained event propagation.

.. versionchanged:: 0.9.0 the ``initiator`` argument is now
             passed as a :class:`.attributes.Event` object, and may be
             modified by backref handlers within a chain of backref-linked
             events.

:return: No return value is defined for this event.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

Nr���r����r���r���r���r&������s����zAttributeEvents.removec�����������������C���s���dS�)a
��Receive a scalar set event.

:param target: the object instance receiving the event.
          If the listener is registered with ``raw=True``, this will
          be the :class:`.InstanceState` object.
        :param value: the value being set.  If this listener
          is registered with ``retval=True``, the listener
          function must return this value, or a new value which
          replaces it.
        :param oldvalue: the previous value being replaced.  This
          may also be the symbol ``NEVER_SET`` or ``NO_VALUE``.
          If the listener is registered with ``active_history=True``,
          the previous value of the attribute will be loaded from
          the database if the existing value is currently unloaded
          or expired.
        :param initiator: An instance of :class:`.attributes.Event`
          representing the initiation of the event.  May be modified
          from its original value by backref handlers in order to control
          chained event propagation.

:return: if the event was registered with ``retval=True``,
         the given value, or a new effective value, should be returned.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

Nr���)r:���r���r����Zoldvaluer����r���r���r����set���s����zAttributeEvents.setc�����������������C���s���dS�)aQ��Receive a scalar "init" event.

This event is invoked when an uninitialized, unpersisted scalar
        attribute is accessed, e.g. read::

x = my_object.some_attribute

The ORM's default behavior when this occurs for an un-initialized
        attribute is to return the value ``None``; note this differs from
        Python's usual behavior of raising ``AttributeError``.    The
        event here can be used to customize what value is actually returned,
        with the assumption that the event listener would be mirroring
        a default generator that is configured on the Core
        :class:`_schema.Column`
        object as well.

Since a default generator on a :class:`_schema.Column`
        might also produce
        a changing value such as a timestamp, the
        :meth:`.AttributeEvents.init_scalar`
        event handler can also be used to **set** the newly returned value, so
        that a Core-level default generation function effectively fires off
        only once, but at the moment the attribute is accessed on the
        non-persisted object.   Normally, no change to the object's state
        is made when an uninitialized attribute is accessed (much older
        SQLAlchemy versions did in fact change the object's state).

If a default generator on a column returned a particular constant,
        a handler might be used as follows::

SOME_CONSTANT = 3.1415926

class MyClass(Base):
                # ...

some_attribute = Column(Numeric, default=SOME_CONSTANT)

@event.listens_for(
                MyClass.some_attribute, "init_scalar",
                retval=True, propagate=True)
            def _init_some_attribute(target, dict_, value):
                dict_['some_attribute'] = SOME_CONSTANT
                return SOME_CONSTANT

Above, we initialize the attribute ``MyClass.some_attribute`` to the
        value of ``SOME_CONSTANT``.   The above code includes the following
        features:

* By setting the value ``SOME_CONSTANT`` in the given ``dict_``,
          we indicate that this value is to be persisted to the database.
          This supersedes the use of ``SOME_CONSTANT`` in the default generator
          for the :class:`_schema.Column`.  The ``active_column_defaults.py``
          example given at :ref:`examples_instrumentation` illustrates using
          the same approach for a changing default, e.g. a timestamp
          generator.    In this particular example, it is not strictly
          necessary to do this since ``SOME_CONSTANT`` would be part of the
          INSERT statement in either case.

* By establishing the ``retval=True`` flag, the value we return
          from the function will be returned by the attribute getter.
          Without this flag, the event is assumed to be a passive observer
          and the return value of our function is ignored.

* The ``propagate=True`` flag is significant if the mapped class
          includes inheriting subclasses, which would also make use of this
          event listener.  Without this flag, an inheriting subclass will
          not use our event handler.

In the above example, the attribute set event
        :meth:`.AttributeEvents.set` as well as the related validation feature
        provided by :obj:`_orm.validates` is **not** invoked when we apply our
        value to the given ``dict_``.  To have these events to invoke in
        response to our newly generated value, apply the value to the given
        object as a normal attribute set operation::

SOME_CONSTANT = 3.1415926

@event.listens_for(
                MyClass.some_attribute, "init_scalar",
                retval=True, propagate=True)
            def _init_some_attribute(target, dict_, value):
                # will also fire off attribute set events
                target.some_attribute = SOME_CONSTANT
                return SOME_CONSTANT

When multiple listeners are set up, the generation of the value
        is "chained" from one listener to the next by passing the value
        returned by the previous listener that specifies ``retval=True``
        as the ``value`` argument of the next listener.

.. versionadded:: 1.1

:param target: the object instance receiving the event.
         If the listener is registered with ``raw=True``, this will
         be the :class:`.InstanceState` object.
        :param value: the value that is to be returned before this event
         listener were invoked.  This value begins as the value ``None``,
         however will be the return value of the previous event handler
         function if multiple listeners are present.
        :param dict\_: the attribute dictionary of this mapped object.
         This is normally the ``__dict__`` of the object, but in all cases
         represents the destination that the attribute system uses to get
         at the actual value of this attribute.  Placing the value in this
         dictionary has the effect that the value will be used in the
         INSERT statement generated by the unit of work.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

:ref:`examples_instrumentation` - see the
            ``active_column_defaults.py`` example.

Nr���)r:���r���r����Zdict_r���r���r����init_scalar	��s����zAttributeEvents.init_scalarc�����������������C���s���dS�)a���Receive a 'collection init' event.

This event is triggered for a collection-based attribute, when
        the initial "empty collection" is first generated for a blank
        attribute, as well as for when the collection is replaced with
        a new one, such as via a set event.

E.g., given that ``User.addresses`` is a relationship-based
        collection, the event is triggered here::

u1 = User()
            u1.addresses.append(a1)  #  <- new collection

and also during replace operations::

u1.addresses = [a2, a3]  #  <- new collection

:param target: the object instance receiving the event.
         If the listener is registered with ``raw=True``, this will
         be the :class:`.InstanceState` object.
        :param collection: the new collection.  This will always be generated
         from what was specified as
         :paramref:`_orm.relationship.collection_class`, and will always
         be empty.
        :param collection_adapter: the :class:`.CollectionAdapter` that will
         mediate internal access to the collection.

.. versionadded:: 1.0.0 the :meth:`.AttributeEvents.init_collection`
           and :meth:`.AttributeEvents.dispose_collection` events supersede
           the :class:`.orm.collection.linker` hook.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

Nr����r:���r���r~���Zcollection_adapterr���r���r����init_collection�	��s����zAttributeEvents.init_collectionc�����������������C���s���dS�)a���Receive a 'collection dispose' event.

This event is triggered for a collection-based attribute when
        a collection is replaced, that is::

u1.addresses.append(a1)

u1.addresses = [a2, a3]  # <- old collection is disposed

The old collection received will contain its previous contents.

.. versionchanged:: 1.2 The collection passed to
           :meth:`.AttributeEvents.dispose_collection` will now have its
           contents before the dispose intact; previously, the collection
           would be empty.

.. versionadded:: 1.0.0 the :meth:`.AttributeEvents.init_collection`
           and :meth:`.AttributeEvents.dispose_collection` events supersede
           the :class:`.collection.linker` hook.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

Nr���r����r���r���r����dispose_collection�	��s����z"AttributeEvents.dispose_collectionc�����������������C���s���dS�)a���Receive a 'modified' event.

This event is triggered when the :func:`.attributes.flag_modified`
        function is used to trigger a modify event on an attribute without
        any specific value being set.

.. versionadded:: 1.2

:param target: the object instance receiving the event.
          If the listener is registered with ``raw=True``, this will
          be the :class:`.InstanceState` object.

:param initiator: An instance of :class:`.attributes.Event`
          representing the initiation of the event.

.. seealso::

:class:`.AttributeEvents` - background on listener options such
            as propagation to subclasses.

Nr���)r:���r���r����r���r���r����modified�	��s����zAttributeEvents.modifiedN)FFFF)r?���r@���rA���rB���rC���r���rD����staticmethodr����rE���r���r3���r����r����r&���r����r����r����r����r����r���r���r���r���r������s*���B

�����+4$w'r����c�������������������@���s>���e�Zd�ZdZdZeZdd��Zdd��Zdd��Z	e
d
d
d��ZdS�)�QueryEventsa���Represent events within the construction of a :class:`_query.Query`
    object.

The events here are intended to be used with an as-yet-unreleased
    inspection system for :class:`_query.Query`.   Some very basic operations
    are possible now, however the inspection system is intended to allow
    complex query manipulations to be automated.

.. versionadded:: 1.0.0

Z	SomeQueryc�����������������C���s���dS�)a���Receive the :class:`_query.Query`
        object before it is composed into a
        core :class:`_expression.Select` object.

This event is intended to allow changes to the query given::

@event.listens_for(Query, "before_compile", retval=True)
            def no_deleted(query):
                for desc in query.column_descriptions:
                    if desc['type'] is User:
                        entity = desc['entity']
                        query = query.filter(entity.deleted == False)
                return query

The event should normally be listened with the ``retval=True``
        parameter set, so that the modified query may be returned.

The :meth:`.QueryEvents.before_compile` event by default
        will disallow "baked" queries from caching a query, if the event
        hook returns a new :class:`_query.Query` object.
        This affects both direct
        use of the baked query extension as well as its operation within
        lazy loaders and eager loaders for relationships.  In order to
        re-establish the query being cached, apply the event adding the
        ``bake_ok`` flag::

@event.listens_for(
                Query, "before_compile", retval=True, bake_ok=True)
            def my_event(query):
                for desc in query.column_descriptions:
                    if desc['type'] is User:
                        entity = desc['entity']
                        query = query.filter(entity.deleted == False)
                return query

When ``bake_ok`` is set to True, the event hook will only be invoked
        once, and not called for subsequent invocations of a particular query
        that is being cached.

.. versionadded:: 1.3.11  - added the "bake_ok" flag to the
           :meth:`.QueryEvents.before_compile` event and disallowed caching via
           the "baked" extension from occurring for event handlers that
           return  a new :class:`_query.Query` object if this flag is not set.

.. seealso::

:meth:`.QueryEvents.before_compile_update`

:meth:`.QueryEvents.before_compile_delete`

:ref:`baked_with_before_compile`

Nr���)r:���r����r���r���r����before_compile�	��s����zQueryEvents.before_compilec�����������������C���s���dS�)a���Allow modifications to the :class:`_query.Query` object within
        :meth:`_query.Query.update`.

Like the :meth:`.QueryEvents.before_compile` event, if the event
        is to be used to alter the :class:`_query.Query` object, it should
        be configured with ``retval=True``, and the modified
        :class:`_query.Query` object returned, as in ::

@event.listens_for(Query, "before_compile_update", retval=True)
            def no_deleted(query, update_context):
                for desc in query.column_descriptions:
                    if desc['type'] is User:
                        entity = desc['entity']
                        query = query.filter(entity.deleted == False)

update_context.values['timestamp'] = datetime.utcnow()
                return query

The ``.values`` dictionary of the "update context" object can also
        be modified in place as illustrated above.

:param query: a :class:`_query.Query` instance; this is also
         the ``.query`` attribute of the given "update context"
         object.

:param update_context: an "update context" object which is
         the same kind of object as described in
         :paramref:`.QueryEvents.after_bulk_update.update_context`.
         The object has a ``.values`` attribute in an UPDATE context which is
         the dictionary of parameters passed to :meth:`_query.Query.update`.
         This
         dictionary can be modified to alter the VALUES clause of the
         resulting UPDATE statement.

.. versionadded:: 1.2.17

.. seealso::

:meth:`.QueryEvents.before_compile`

:meth:`.QueryEvents.before_compile_delete`

Nr���)r:���r����r����r���r���r����before_compile_update0
��s����z!QueryEvents.before_compile_updatec�����������������C���s���dS�)a���Allow modifications to the :class:`_query.Query` object within
        :meth:`_query.Query.delete`.

Like the :meth:`.QueryEvents.before_compile` event, this event
        should be configured with ``retval=True``, and the modified
        :class:`_query.Query` object returned, as in ::

@event.listens_for(Query, "before_compile_delete", retval=True)
            def no_deleted(query, delete_context):
                for desc in query.column_descriptions:
                    if desc['type'] is User:
                        entity = desc['entity']
                        query = query.filter(entity.deleted == False)
                return query

:param query: a :class:`_query.Query` instance; this is also
         the ``.query`` attribute of the given "delete context"
         object.

:param delete_context: a "delete context" object which is
         the same kind of object as described in
         :paramref:`.QueryEvents.after_bulk_delete.delete_context`.

.. versionadded:: 1.2.17

.. seealso::

:meth:`.QueryEvents.before_compile`

:meth:`.QueryEvents.before_compile_update`

Nr���)r:���r����r����r���r���r����before_compile_delete^
��s����z!QueryEvents.before_compile_deleteFc��������������������sP���|j����s$���fdd�}|�|�}n��fdd�}|�|�}||_|jf�|��d�S�)Nc���������������������s(����s|�d�}��|�|��|S���|�|�S�d�S�r����r���)r���r2���r�����r���rw���r���r���r^����
��s
����
z!QueryEvents._listen.<locals>.wrapc���������������������s
�����|�|�S�r���r���r����r����r���r���r^����
��s����)r+���r/���Z_bake_okr0���)r���r1���rw���Zbake_okr2���r^���r���r����r���r3����
��s����
zQueryEvents._listenN)FF)r?���r@���rA���rB���rC���r	���rD���r����r����r����rE���r3���r���r���r���r���r�����	��s���7.#r����)%rB���r,�����r���r���r����
attributesr����baser���r����r	���Zscopingr
���r����r���r���r���r���r���Zutil.compatr���r����r���r����r���rK���Z
RefCollectionrs���rM���r����r����r����r����r����r����r����r���r���r���r����<module>���sT���Y���E�����-���������g

Name	Type	Size	Owner/Group	Permission	Last Modified	Actions
.	dir	-	169531/169531	0755	2025-10-03 03:39:18
..	dir	-	169531/169531	0755	2025-10-03 03:39:17
__init__.cpython-38.pyc	text/x-bytecode.python	8.66 KB	169531/169531	0644	2025-10-03 03:39:17
attributes.cpython-38.pyc	text/x-bytecode.python	51.26 KB	169531/169531	0644	2025-10-03 03:39:17
base.cpython-38.pyc	text/x-bytecode.python	13.03 KB	169531/169531	0644	2025-10-03 03:39:17
collections.cpython-38.pyc	text/x-bytecode.python	51.41 KB	169531/169531	0644	2025-10-03 03:39:17
dependency.cpython-38.pyc	text/x-bytecode.python	23.14 KB	169531/169531	0644	2025-10-03 03:39:17
deprecated_interfaces.cpython-38.pyc	text/x-bytecode.python	19.31 KB	169531/169531	0644	2025-10-03 03:39:17
descriptor_props.cpython-38.pyc	text/x-bytecode.python	28.63 KB	169531/169531	0644	2025-10-03 03:39:17
dynamic.cpython-38.pyc	text/x-bytecode.python	11.62 KB	169531/169531	0644	2025-10-03 03:39:17
evaluator.cpython-38.pyc	text/x-bytecode.python	5.53 KB	169531/169531	0644	2025-10-03 03:39:17
events.cpython-38.pyc	text/x-bytecode.python	103.61 KB	169531/169531	0644	2025-10-03 03:39:17
exc.cpython-38.pyc	text/x-bytecode.python	6.9 KB	169531/169531	0644	2025-10-03 03:39:17
identity.cpython-38.pyc	text/x-bytecode.python	10.93 KB	169531/169531	0644	2025-10-03 03:39:17
instrumentation.cpython-38.pyc	text/x-bytecode.python	16.85 KB	169531/169531	0644	2025-10-03 03:39:17
interfaces.cpython-38.pyc	text/x-bytecode.python	25.99 KB	169531/169531	0644	2025-10-03 03:39:17
loading.cpython-38.pyc	text/x-bytecode.python	18.1 KB	169531/169531	0644	2025-10-03 03:39:17
mapper.cpython-38.pyc	text/x-bytecode.python	89 KB	169531/169531	0644	2025-10-03 03:39:18
path_registry.cpython-38.pyc	text/x-bytecode.python	12.68 KB	169531/169531	0644	2025-10-03 03:39:18
persistence.cpython-38.pyc	text/x-bytecode.python	38.28 KB	169531/169531	0644	2025-10-03 03:39:18
properties.cpython-38.pyc	text/x-bytecode.python	11.7 KB	169531/169531	0644	2025-10-03 03:39:18
query.cpython-38.pyc	text/x-bytecode.python	139.87 KB	169531/169531	0644	2025-10-03 03:39:18
relationships.cpython-38.pyc	text/x-bytecode.python	100.98 KB	169531/169531	0644	2025-10-03 03:39:18
scoping.cpython-38.pyc	text/x-bytecode.python	6.17 KB	169531/169531	0644	2025-10-03 03:39:18
session.cpython-38.pyc	text/x-bytecode.python	107.73 KB	169531/169531	0644	2025-10-03 03:39:18
state.cpython-38.pyc	text/x-bytecode.python	26.4 KB	169531/169531	0644	2025-10-03 03:39:18
strategies.cpython-38.pyc	text/x-bytecode.python	51.22 KB	169531/169531	0644	2025-10-03 03:39:18
strategy_options.cpython-38.pyc	text/x-bytecode.python	44.35 KB	169531/169531	0644	2025-10-03 03:39:18
sync.cpython-38.pyc	text/x-bytecode.python	3.79 KB	169531/169531	0644	2025-10-03 03:39:18
unitofwork.cpython-38.pyc	text/x-bytecode.python	19.21 KB	169531/169531	0644	2025-10-03 03:39:18
util.cpython-38.pyc	text/x-bytecode.python	38.41 KB	169531/169531	0644	2025-10-03 03:39:18

Team Anon Force

https://t.me/Professor6T9x