File: //usr/local/lib/python3.10/dist-packages/sqlalchemy/orm/__pycache__/events.cpython-310.pyc
o
���g%� � @ s� U d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z dd lm
Z
dd
lm Z dd lm Z dd lm
Z
dd
lmZ ddlmZ ddlmZ ddlZddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z ddl m Z ddl m Z dd l m Z dd l!m"Z" dd l#m$Z$ dd l#m%Z% d d!lm&Z& d d"lm'Z' d d#lm(Z( d d$l&m)Z) d d%l*m+Z+ d d&l,m-Z- e�rNdd'lm.Z. dd(l/m0Z0 dd)l/m1Z1 dd*l/m2Z2 dd+l/m3Z3 dd,lm4Z4 dd-lm5Z5 dd.l#m6Z6 dd/l#m7Z7 dd0l8m9Z9 d d1l:m;Z; d d2l<m=Z= d d3l<m>Z> d d4l*m?Z? d d5l@mAZA d d6lBmCZC d d7lDmEZE d d8lDmFZF d d9lGmHZH d d:lImJZJ ed;ed<�ZKed=e)d<�ZLG d>d?� d?e&jMe �ZNG d@dA� dA�ZOG dBdC� dCe&jMee �ZPG dDdE� dEe&jQe+ �ZRG dFdG� dGeRe+ �ZSG dHdI� dIe&jMejHe �ZTG dJdK� dKeRe+ �ZUeV� ZWdLeXdM< G dNdO� dOe&jMe$ �ZYG dPdQ� dQe&jMee �ZZG dRdS� dSe&jMe e �Z[dS )TzORM event interfaces.
� )� annotations)�Any)�Callable)�
Collection)�Dict)�Generic)�Iterable)�Optional)�Sequence)�Set)�Type)�
TYPE_CHECKING)�TypeVar)�UnionN� )�instrumentation)�
interfaces)� mapperlib)�QueryableAttribute��_mapper_or_none)�NO_KEY)� ClassManager)�InstrumentationFactory)�
BulkDelete)�
BulkUpdate)�Query)�scoped_session)�Session)� sessionmaker� )�event)�exc)�util)� EventTarget)�_ET)�inspect_getfullargspec)�
ReferenceType)�
_InstanceDict)�_InternalEntityType)�_O)�_T)�Event)�EventConstants)�ORMExecuteState)�SessionTransaction)�UOWTransaction)�
Connection)� _Dispatch)�_HasEventsDispatch)� _EventKey)�CollectionAdapter)� QueryContext)� DeclarativeAttributeIntercept)�DeclarativeMeta)�Mapper)�
InstanceState�_KT)�bound�_ET2c sl e Zd ZdZdZeZed#d d
��Ze d$d%dd��Z ed&� fdd� �Z
d'dd�Z d'dd �Z d(d!d"�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.
�
SomeBaseClass�target�;Union[InstrumentationFactory, Type[InstrumentationFactory]]�
identifier�str�return�EOptional[Union[InstrumentationFactory, Type[InstrumentationFactory]]]c C s t |t�r t|�S d S �N)�
isinstance�type�_InstrumentationEventsHold��clsr@ rB � rL �@/usr/local/lib/python3.10/dist-packages/sqlalchemy/orm/events.py� _accept_withe s
z"InstrumentationEvents._accept_withT� event_key�
_EventKey[_T]� propagate�bool�kwr �Nonec sh |j |j|j��� d� ��fdd� �d��fd d
� }t��j|��|�tj�� ��j
di |�� d S )N�
target_clsrH �argr rD �
Optional[Any]c sP �� }|d u r d S �rt | |�r� | g|�R � S �s&| |u r&� | g|�R � S d S rF )�
issubclass)rU rV �
listen_cls)�fnrQ r@ rL rM �listen� s z-InstrumentationEvents._listen.<locals>.listen�ref�ReferenceType[_T]rT c s, t j�d � �tj�}ttjj� ��|� d S rF )r! �registryr4 r �_instrumentation_factory�getattr�dispatch�remove)r\ �key)rB r[ rL rM rb � s �� z-InstrumentationEvents._listen.<locals>.remove)rU rH rV r rD rW )r\ r] rD rT rL ) �dispatch_targetrB �
_listen_fn�weakrefr\ �class_�with_dispatch_targetr r_ � with_wrapper� base_listen)rK rO rQ rS rb rL )rZ rB r[ rQ r@ rM �_listenx s
� ��
�z InstrumentationEvents._listenc s t � �� tjj�� d S rF )�super�_clearr r_ ra �rK �� __class__rL rM rm � s
z InstrumentationEvents._clearrK �ClassManager[_O]c C � dS )z�Called after the given class is instrumented.
To get at the :class:`.ClassManager`, use
:func:`.manager_of_class`.
NrL ��selfrK rL rL rM �class_instrument� � z&InstrumentationEvents.class_instrumentc C rr )z�Called before the given class is uninstrumented.
To get at the :class:`.ClassManager`, use
:func:`.manager_of_class`.
NrL rs rL rL rM �class_uninstrument� rv z(InstrumentationEvents.class_uninstrumentrc r; �instr* c C rr )z)Called when an attribute is instrumented.NrL )rt rK rc rx rL rL rM �attribute_instrument� rv z*InstrumentationEvents.attribute_instrument)r@ rA rB rC rD rE )T)rO rP rQ rR rS r rD rT �rD rT )rK rq rD rT )rK rq rc r; rx r* rD rT )�__name__�
__module__� __qualname__�__doc__�_target_class_docr �_dispatch_target� classmethodrN rk rm ru rw ry �
__classcell__rL rL ro rM r> L s �+
r> c @ s$ e Zd ZdZd dd�Ze�e�ZdS )
rI zwtemporary marker object used to transfer from _accept_with() to
_listen() on the InstrumentationEvents class.
rg rH rD rT c C �
|| _ d S rF �rg �rt rg rL rL rM �__init__� �
z#_InstrumentationEventsHold.__init__N)rg rH rD rT ) r{ r| r} r~ r� r! �
dispatcherr> ra rL rL rL rM rI � s
rI c s� e Zd ZdZdZeZedBd d
��Zee �
d �dCdd���Z e dDdEd d ��Z edF� fd d � �Z
dGd#d$�ZdHd(d)�ZdHd*d+�ZdId.d/�ZdId0d1�ZdJd4d5�ZdKd8d9�ZdLd:d;�ZdMd>d?�ZdMd@dA�Z� ZS )N�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 indicates 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
� SomeClassrg �;Union[DeclarativeAttributeIntercept, DeclarativeMeta, type]� classmanagerrq rD rT c C � t �||� d S rF )�_InstanceEventsHold�populate)rK rg r� rL rL rM �_new_classmanager_instance � z)InstanceEvents._new_classmanager_instance�sqlalchemy.ormr@ �1Union[ClassManager[Any], Type[ClassManager[Any]]]rB rC �;Optional[Union[ClassManager[Any], Type[ClassManager[Any]]]]c C sz t jj}t|t�r |S t|tj�r|jS ||ju r!t � dd� tS t|t
�r;t |tj�r.tS t �
|�}|r7|S t|�S d S �Nz�The `sqlalchemy.orm.mapper()` symbol is deprecated and will be removed in a future release. For the mapper-wide event target, use the 'sqlalchemy.orm.Mapper' class.z2.0)r# � preloaded�ormrG r r r9 �
class_manager�mapper�warn_deprecatedrH rX r �opt_manager_of_classr� )rK r@ rB r� �managerrL rL rM rN s&
�
zInstanceEvents._accept_withFrO � _EventKey[ClassManager[Any]]�rawrR rQ �restore_load_contextrS r c st |j |j}� �r �rd
� ��fdd � }|�|�}|jdd
|i|�� |r6|�d �D ]
}|�|�jd d � q*d S d S )N�state�InstanceState[_O]rV r rS rD rW c sN �s| � � }n| }�r| j}z� |g|�R i |��W �r || _S S �r&|| _w rF ��obj�runid)r� rV rS r@ r� �rZ r� r� rL rM �wrap9 s
�z$InstanceEvents._listen.<locals>.wraprQ T�rQ )r� r� rV r rS r rD rW rL )rd re ri rj �subclass_managersrh ) rK rO r� rQ r� rS r@ r� �mgrrL r� rM rk , s
�zInstanceEvents._listenc � t � �� t�� d S rF )rl rm r� rn ro rL rM rm P �
zInstanceEvents._clearr� rK �Type[_O]c C rr )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.
NrL )rt r� rK rL rL rM �
first_initU rv zInstanceEvents.first_initr* �args�kwargsc C rr )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`
NrL �rt r@ r� r� rL rL rM �init_ rv zInstanceEvents.initc C rr )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`
NrL r� rL rL rM � init_failure~ rv zInstanceEvents.init_failure�contextr6 c C rr )a� receive an object instance after it was the subject of a merge()
call, when load=False was passed.
The target would be the already-loaded object in the Session which
would have had its attributes overwritten by the incoming object. This
overwrite operation does not use attribute events, instead just
populating dict directly. Therefore the purpose of this event is so
that extensions like sqlalchemy.ext.mutable know that object state has
changed and incoming state needs to be set up for "parents" etc.
This functionality is acceptable to be made public in a later release.
.. versionadded:: 1.4.41
NrL �rt r@ r� rL rL rM �_sa_event_merge_wo_load� rv z&InstanceEvents._sa_event_merge_wo_loadc C rr )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::
:ref:`mapped_class_load_events`
:meth:`.InstanceEvents.init`
:meth:`.InstanceEvents.refresh`
:meth:`.SessionEvents.loaded_as_persistent`
NrL r� rL rL rM �load� rv zInstanceEvents.load�attrs�Optional[Iterable[str]]c C rr )a� 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::
:ref:`mapped_class_load_events`
:meth:`.InstanceEvents.load`
NrL )rt r@ r� r� rL rL rM �refresh� rv zInstanceEvents.refresh�
flush_contextr0 c C rr )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.
: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:`mapped_class_load_events`
:ref:`orm_server_defaults`
:ref:`metadata_defaults_toplevel`
NrL )rt r@ r� r� rL rL rM �
refresh_flush rv z InstanceEvents.refresh_flushc C rr )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.
: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 attrs: sequence of attribute
names which were expired, or None if all attributes were
expired.
NrL )rt r@ r� rL rL rM �expireO rv zInstanceEvents.expire�
state_dictr( c C rr )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.
NrL �rt r@ r� rL rL rM �pickle` rv zInstanceEvents.picklec C rr )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.
NrL r� rL rL rM �unpicklen rv zInstanceEvents.unpickle)rg r� r� rq rD rT )r@ r� rB rC rD r� �FFF) rO r� r� rR rQ rR r� rR rS r rD rT rz )r� rq rK r� rD rT )r@ r* r� r r� r rD rT )r@ r* r� r6 rD rT )r@ r* r� r6 r� r� rD rT )r@ r* r� r0 r� r� rD rT )r@ r* r� r� rD rT )r@ r* r� r( rD rT )r{ r| r} r~ r r r� r� r� r# �preload_modulerN rk rm r� r� r� r� r� r� r� r� r� r� r� rL rL ro rM r� � s4 1 !�#
!
J
$
/
r� c @ s^ e Zd ZU dZded< ddd �Zedd
d ��ZG d d
� d
ee �Z
ddd�Z eddd��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.
�#weakref.WeakKeyDictionary[Any, Any]� all_holdsrg r� rD rT c C r� rF r� r� rL rL rM r� � s
z_EventsHold.__init__c C s | j �� d S rF )r� �clearrn rL rL rM rm � s z_EventsHold._clearc @ s0 e Zd ZU dZded< e dddd��ZdS )z_EventsHold.HoldEventsNzOptional[Type[_ET2]]r� FrO �_EventKey[_ET2]r� rR rQ �retvalrS r rD rT c K s� |j }|j|jv r|j|j }ni }|j|j< tj�||� |||||f||j< |r\t|j�� �}|r^|� d�} |�
| �� � |� | �}
|
d urX|� |
�j
d|d|d�|�� |s4d S d S d S )Nr F�r� rQ r� rL )rd rg r� r! r^ �_stored_in_collection�_key�list�__subclasses__�pop�extend�resolverh r[ ) rK rO r� rQ r� rS r@ �
collection�stack�subclass�subjectrL rL rM rk � s4
�
����z _EventsHold.HoldEvents._listenr� ) rO r� r� rR rQ rR r� rR rS r rD rT )r{ r| r} r� �__annotations__r� rk rL rL rL rM �
HoldEvents� s
�r� rO �_EventKey[_ET]c C s, |j }t|t�r|j|j }||j= d S d S rF )rd rG r� r� rg r� )rt rO r@ r� rL rL rM rb � s
�z_EventsHold.remover� �#Union[ClassManager[_O], Mapper[_O]]c
C sf |j D ]-}|| jv r0| j| }|�� D ] \}}}}} |s ||u r/|�|�jd|d|d�| �� qqd S )NFr� rL )�__mro__r� �valuesrh r[ )
rK rg r� r� r� rO r� rQ r� rS rL rL rM r� � s$
� ����z_EventsHold.populateN)rg r� rD rT rz )rO r� rD rT )rg r� r� r� rD rT )
r{ r| r} r~ r� r� r� rm r r= r� rb r� rL rL rL rM r� } s
)r� c @ sJ e Zd ZU e�� Zded< d dd�ZG d d
� d
ej e
e �Z e
�e �Zd S )
r� r� r� rg r� rD �Optional[ClassManager[_O]]c C s
t �|�S rF )r r� r� rL rL rM r� � r� z_InstanceEventsHold.resolvec @ � e Zd ZdS )z&_InstanceEventsHold.HoldInstanceEventsN�r{ r| r} rL rL rL rM �HoldInstanceEvents� � r� N)rg r� rD r� )r{ r| r} rf �WeakKeyDictionaryr� r� r� r� r� r% r� r� r! r� ra rL rL rL rM r� � s
�
r� c s� e Zd ZdZdZejZed<d d
��Z ee
� d �d=dd���Z e d>d?d d ��Z
ed@� fd d � �ZdAd!d"�ZdAd#d$�ZdAd%d&�ZdAd'd(�Zd@d)d*�Zd@d+d,�ZdBd0d1�ZdBd2d3�ZdBd4d5�ZdBd6d7�ZdBd8d9�ZdBd:d;�Z� ZS )C� 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.execute(
text("select my_special_function(%d)" % target.special_number)
).scalar()
# 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:
* 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 indicates listening for all
mappers.
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.
r� rg r� r� �
Mapper[_O]rD rT c C r� rF )�_MapperEventsHoldr� )rK rg r� rL rL rM �_new_mapper_instance0 r� z!MapperEvents._new_mapper_instancer� r@ �9Union[mapperlib.Mapper[Any], Type[mapperlib.Mapper[Any]]]rB rC �COptional[Union[mapperlib.Mapper[Any], Type[mapperlib.Mapper[Any]]]]c C s^ t jj}||ju rt �dd� tjS t|t�r-t |tj�r |S t
|�}|d ur)|S t |�S |S r� ) r# r� r� r� r� r r9 rG rH rX r r� )rK r@ rB r� r� rL rL rM rN 8 s
�
zMapperEvents._accept_withFrO r� r� rR r� rQ rS r c s� |j |j|j}}� |dv r|tjurt�d� �r �sL�s=t| |�}z
t|�d � d�d �W n t
y< d �Y nw d� ���fd
d � } |� | �}|rc|j D ]}
|�
|
�jdd d
i|�� qQd S |jdi |�� d S )N)�before_configured�after_configuredzf'before_configured' and 'after_configured' ORM events only invoke with the Mapper class as the target.r r@ r rV r rS rD c sJ �s�d urt | �} | � �� | �< �s � | i |�� tjS � | i |��S rF )r� r� r � EXT_CONTINUE�rV rS �rZ r� r� � target_indexrL rM r� x s z"MapperEvents._listen.<locals>.wraprQ T�rV r rS r rD r rL )rd rB re r r9 r# �warnr` r& �index�
ValueErrorri �self_and_descendantsrh rj ) rK rO r� r� rQ rS r@ rB �methr� r� rL r� rM rk U s:
�
�
� �
���zMapperEvents._listenc r� rF )rl rm r� rn ro rL rM rm � r� zMapperEvents._clearr� c C rr )an 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. To
receive an event within initial mapper construction where basic
state is available such as the :attr:`_orm.Mapper.attrs` collection,
the :meth:`_orm.MapperEvents.after_mapper_constructed` event may
be a better choice.
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.
.. seealso::
:meth:`_orm.MapperEvents.after_mapper_constructed`
NrL �rt r� rg rL rL rM �instrument_class� rv z MapperEvents.instrument_classc C rr )a� Receive a class and mapper when the :class:`_orm.Mapper` has been
fully constructed.
This event is called after the initial constructor for
:class:`_orm.Mapper` completes. This occurs after the
:meth:`_orm.MapperEvents.instrument_class` event and after the
:class:`_orm.Mapper` has done an initial pass of its arguments
to generate its collection of :class:`_orm.MapperProperty` objects,
which are accessible via the :meth:`_orm.Mapper.get_property`
method and the :attr:`_orm.Mapper.iterate_properties` attribute.
This event differs from the
:meth:`_orm.MapperEvents.before_mapper_configured` event in that it
is invoked within the constructor for :class:`_orm.Mapper`, rather
than within the :meth:`_orm.registry.configure` process. Currently,
this event is the only one which is appropriate for handlers that
wish to create additional mapped classes in response to the
construction of this :class:`_orm.Mapper`, which will be part of the
same configure step when :meth:`_orm.registry.configure` next runs.
.. versionadded:: 2.0.2
.. seealso::
:ref:`examples_versioning` - an example which illustrates the use
of the :meth:`_orm.MapperEvents.before_mapper_configured`
event to create new mappers to record change-audit histories on
objects.
NrL r� rL rL rM �after_mapper_constructed� rv z%MapperEvents.after_mapper_constructedc C rr )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 "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`
NrL r� rL rL rM �before_mapper_configured� rv z%MapperEvents.before_mapper_configuredc C rr )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`
NrL r� rL rL rM �mapper_configured rv z MapperEvents.mapper_configuredc C rr )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,
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(): ...
.. seealso::
:meth:`.MapperEvents.before_mapper_configured`
:meth:`.MapperEvents.mapper_configured`
:meth:`.MapperEvents.after_configured`
NrL �rt rL rL rM r� > rv z MapperEvents.before_configuredc C rr )a3 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.
This event can **only** be applied to the :class:`_orm.Mapper` class,
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, "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`
NrL r� rL rL rM r� q rv z MapperEvents.after_configured�
connectionr1 r* c C rr )a# Receive an object instance before an INSERT statement
is emitted corresponding to that instance.
.. note:: this event **only** applies to the
:ref:`session flush operation <session_flushing>`
and does **not** apply to the ORM DML operations described at
:ref:`orm_expression_update_delete`. To intercept ORM
DML events, use :meth:`_orm.SessionEvents.do_orm_execute`.
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 :class:`_orm.Mapper` object 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`
NrL �rt r� r� r@ rL rL rM �
before_insert� rv zMapperEvents.before_insertc C rr )a Receive an object instance after an INSERT statement
is emitted corresponding to that instance.
.. note:: this event **only** applies to the
:ref:`session flush operation <session_flushing>`
and does **not** apply to the ORM DML operations described at
:ref:`orm_expression_update_delete`. To intercept ORM
DML events, use :meth:`_orm.SessionEvents.do_orm_execute`.
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
:class:`_orm.Mapper` object 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`
NrL r� rL rL rM � after_insert� rv zMapperEvents.after_insertc C rr )a� Receive an object instance before an UPDATE statement
is emitted corresponding to that instance.
.. note:: this event **only** applies to the
:ref:`session flush operation <session_flushing>`
and does **not** apply to the ORM DML operations described at
:ref:`orm_expression_update_delete`. To intercept ORM
DML events, use :meth:`_orm.SessionEvents.do_orm_execute`.
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 :class:`_orm.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 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`
NrL r� rL rL rM �
before_update rv zMapperEvents.before_updatec C rr )a� Receive an object instance after an UPDATE statement
is emitted corresponding to that instance.
.. note:: this event **only** applies to the
:ref:`session flush operation <session_flushing>`
and does **not** apply to the ORM DML operations described at
:ref:`orm_expression_update_delete`. To intercept ORM
DML events, use :meth:`_orm.SessionEvents.do_orm_execute`.
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 :class:`_orm.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 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`
NrL r� rL rL rM � after_update[ rv zMapperEvents.after_updatec C rr )a� Receive an object instance before a DELETE statement
is emitted corresponding to that instance.
.. note:: this event **only** applies to the
:ref:`session flush operation <session_flushing>`
and does **not** apply to the ORM DML operations described at
:ref:`orm_expression_update_delete`. To intercept ORM
DML events, use :meth:`_orm.SessionEvents.do_orm_execute`.
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::
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 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`
NrL r� rL rL rM �
before_delete� rv zMapperEvents.before_deletec C rr )a� Receive an object instance after a DELETE statement
has been emitted corresponding to that instance.
.. note:: this event **only** applies to the
:ref:`session flush operation <session_flushing>`
and does **not** apply to the ORM DML operations described at
:ref:`orm_expression_update_delete`. To intercept ORM
DML events, use :meth:`_orm.SessionEvents.do_orm_execute`.
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::
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 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`
NrL r� rL rL rM � after_delete� rv zMapperEvents.after_delete)rg r� r� r� rD rT )r@ r� rB rC rD r� r� ) rO r� r� rR r� rR rQ rR rS r rD rT rz )r� r� rg r� rD rT )r� r� r� r1 r@ r* rD rT ) r{ r| r} r~ r r r9 r� r� r� r# r� rN rk rm r� r� r� r� r� r� r� r� r� r� r� r r� rL rL ro rM r� � s8 B �6
"
5
6
3
5
6
6
I
H0r� c @ s@ e Zd Ze�� Zd
dd�ZG dd� deje e
�Z e �
e �Zd S ) r� rg �(Union[Type[_T], _InternalEntityType[_T]]rD �Optional[Mapper[_T]]c C s t |�S rF r r� rL rL rM r� s z_MapperEventsHold.resolvec @ r� )z"_MapperEventsHold.HoldMapperEventsNr� rL rL rL rM �HoldMapperEvents r� r N)rg r rD r )r{ r| r} rf r� r� r� r� r� r% r� r r! r� ra rL rL rL rM r� s
r� zSet[str]�$_sessionevents_lifecycle_event_namesc @ s� e Zd ZdZdZeZdbdd�Zedcd
d��Z eddd�dddd��Z
dedd �Z dfd!d"�Z dfd#d$�Z
dgd%d&�Zdgd'd(�Zdgd)d*�Zdhd,d-�Zdid2d3�Zdjd4d5�Zdjd6d7�Zdkd:d;�Zedld>d?��Zedld@dA��Ze�dBg dC�dDdE� �dmdGdH��Ze�dBg dC�dIdE� �dndKdL��ZedldMdN��Z edldOdP��Z edldQdR��Z edldSdT��Z edldUdV��Z edldWdX��Z!edldYdZ��Z"edld[d\��Z#edld]d^��Z$edld_d`��Z%daS )o�
SessionEventsat 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
�SomeSessionClassOrObjectrZ �-Callable[[SessionEvents, Session, Any], None]rD c C s t �| j� | S rF )r �addr{ �rZ rL rL rM �_lifecycle_eventD s z SessionEvents._lifecycle_eventr@ r rB rC �Union[Session, type]c C s� t |t�r |j}t |t�s t |t�rt|t�s t�d��t |t�r$|j S t |t�r9t|t�r0tS t|t�r7|S d S t |t�r@|S t
|d�rK|� � d S t j
�||�S )NzrSession event listen on a scoped_session requires that its creation callable is associated with the Session class.�_no_async_engine_events)rG r �session_factoryr rH rX r r" �
ArgumentErrorrg �hasattrr r! �EventsrN rJ rL rL rM rN J s.
���
�
zSessionEvents._accept_withF)r� r� rO r� rR r� rS rT c sL |j tv }|r �r �r |j� d � ��fd
d � }|�|�}|jd
i |�� d S )N�sessionr r� r� rV r rS rD rW c s\ �s
|� � }|d u r d S n|}�r|j}z� | |g|�R i |��W �r'||_S S �r-||_w rF r� )r r� rV rS r@ r� r� rL rM r� y s ��z#SessionEvents._listen.<locals>.wrap)
r r r� r� rV r rS r rD rW rL )rB r re ri rj )rK rO r� r� rS �is_instance_eventr� rL r� rM rk h s
�
zSessionEvents._listen�orm_execute_stater. c C rr )aV Intercept statement executions that occur on behalf of an
ORM :class:`.Session` object.
This event is invoked for all top-level SQL statements invoked from the
:meth:`_orm.Session.execute` method, as well as related methods such as
:meth:`_orm.Session.scalars` and :meth:`_orm.Session.scalar`. As of
SQLAlchemy 1.4, all ORM queries that run through the
:meth:`_orm.Session.execute` method as well as related methods
:meth:`_orm.Session.scalars`, :meth:`_orm.Session.scalar` etc.
will participate in this event.
This event hook does **not** apply to the queries that are
emitted internally within the ORM flush process, i.e. the
process described at :ref:`session_flushing`.
.. note:: The :meth:`_orm.SessionEvents.do_orm_execute` event hook
is triggered **for ORM statement executions only**, meaning those
invoked via the :meth:`_orm.Session.execute` and similar methods on
the :class:`_orm.Session` object. It does **not** trigger for
statements that are invoked by SQLAlchemy Core only, i.e. statements
invoked directly using :meth:`_engine.Connection.execute` or
otherwise originating from an :class:`_engine.Engine` object without
any :class:`_orm.Session` involved. To intercept **all** SQL
executions regardless of whether the Core or ORM APIs are in use,
see the event hooks at :class:`.ConnectionEvents`, such as
:meth:`.ConnectionEvents.before_execute` and
:meth:`.ConnectionEvents.before_cursor_execute`.
Also, this event hook does **not** apply to queries that are
emitted internally within the ORM flush process,
i.e. the process described at :ref:`session_flushing`; to
intercept steps within the flush process, see the event
hooks described at :ref:`session_persistence_events` as
well as :ref:`session_persistence_mapper`.
This event is a ``do_`` event, meaning it has the capability to replace
the operation that the :meth:`_orm.Session.execute` method normally
performs. The intended use for this includes sharding and
result-caching schemes which may seek to invoke the same statement
across multiple database connections, returning a result that is
merged from each of them, or which don't invoke the statement at all,
instead returning data from a cache.
The hook intends to replace the use of the
``Query._execute_and_instances`` method that could be subclassed prior
to SQLAlchemy 1.4.
:param orm_execute_state: an instance of :class:`.ORMExecuteState`
which contains all information about the current execution, as well
as helper functions used to derive other commonly required
information. See that object for details.
.. seealso::
:ref:`session_execute_events` - top level documentation on how
to use :meth:`_orm.SessionEvents.do_orm_execute`
:class:`.ORMExecuteState` - the object passed to the
:meth:`_orm.SessionEvents.do_orm_execute` event which contains
all information about the statement to be invoked. It also
provides an interface to extend the current statement, options,
and parameters as well as an option that allows programmatic
invocation of the statement at any point.
:ref:`examples_session_orm_events` - includes examples of using
:meth:`_orm.SessionEvents.do_orm_execute`
:ref:`examples_caching` - an example of how to integrate
Dogpile caching with the ORM :class:`_orm.Session` making use
of the :meth:`_orm.SessionEvents.do_orm_execute` event hook.
:ref:`examples_sharding` - the Horizontal Sharding example /
extension relies upon the
:meth:`_orm.SessionEvents.do_orm_execute` event hook to invoke a
SQL statement on multiple backends and return a merged result.
.. versionadded:: 1.4
NrL )rt r rL rL rM �do_orm_execute� rv z SessionEvents.do_orm_executer r � transactionr/ c C rr )az 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`
NrL �rt r r rL rL rM �after_transaction_create� rv z&SessionEvents.after_transaction_createc C rr )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`.
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_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`
NrL r rL rL rM �after_transaction_end rv z#SessionEvents.after_transaction_endc C rr )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`
NrL �rt r rL rL rM �
before_commit7 rv zSessionEvents.before_commitc C rr )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`
NrL r rL rL rM � after_commitS rv zSessionEvents.after_commitc C rr )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`.
NrL r rL rL rM �after_rollbackw rv z SessionEvents.after_rollback�previous_transactionc C rr )a� 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(text("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.
NrL )rt r r rL rL rM �after_soft_rollback� rv z!SessionEvents.after_soft_rollbackr� r0 � instances�Optional[Sequence[_O]]c C rr )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`
NrL )rt r r� r rL rL rM � before_flush� rv zSessionEvents.before_flushc C rr )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`
NrL �rt r r� rL rL rM � after_flush� rv zSessionEvents.after_flushc C rr )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`
NrL r" rL rL rM �after_flush_postexec� rv z"SessionEvents.after_flush_postexecr� r1 c C rr )ap Execute after a transaction is begun on a connection.
.. note:: This event is called within the process of the
:class:`_orm.Session` modifying its own internal state.
To invoke SQL operations within this hook, use the
:class:`_engine.Connection` provided to the event;
do not run SQL operations using the :class:`_orm.Session`
directly.
: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`
NrL )rt r r r� rL rL rM � after_begin� rv zSessionEvents.after_begin�instancer* c C rr )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`
NrL �rt r r& rL rL rM �
before_attach rv zSessionEvents.before_attachc C rr )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`
NrL r' rL rL rM � after_attach( rv zSessionEvents.after_attachz0.9)r �query�
query_context�resultc C � | j | jd | jfS rF �r r* r, )�update_contextrL rL rM �<lambda>D �
�zSessionEvents.<lambda>r/ c C rr )aU Event for after the legacy :meth:`_orm.Query.update` method
has been called.
.. legacy:: The :meth:`_orm.SessionEvents.after_bulk_update` method
is a legacy event hook as of SQLAlchemy 2.0. The event
**does not participate** in :term:`2.0 style` invocations
using :func:`_dml.update` documented at
:ref:`orm_queryguide_update_delete_where`. For 2.0 style use,
the :meth:`_orm.SessionEvents.do_orm_execute` hook will intercept
these calls.
: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`.
* ``result`` the :class:`_engine.CursorResult`
returned as a result of the
bulk UPDATE operation.
.. versionchanged:: 1.4 the update_context no longer has a
``QueryContext`` object associated with it.
.. seealso::
:meth:`.QueryEvents.before_compile_update`
:meth:`.SessionEvents.after_bulk_delete`
NrL )rt r/ rL rL rM �after_bulk_updateA rv z SessionEvents.after_bulk_updatec C r- rF r. )�delete_contextrL rL rM r0 r r1 r3 c C rr )a� Event for after the legacy :meth:`_orm.Query.delete` method
has been called.
.. legacy:: The :meth:`_orm.SessionEvents.after_bulk_delete` method
is a legacy event hook as of SQLAlchemy 2.0. The event
**does not participate** in :term:`2.0 style` invocations
using :func:`_dml.delete` documented at
:ref:`orm_queryguide_update_delete_where`. For 2.0 style use,
the :meth:`_orm.SessionEvents.do_orm_execute` hook will intercept
these calls.
: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.
* ``result`` the :class:`_engine.CursorResult`
returned as a result of the
bulk DELETE operation.
.. versionchanged:: 1.4 the update_context no longer has a
``QueryContext`` object associated with it.
.. seealso::
:meth:`.QueryEvents.before_compile_delete`
:meth:`.SessionEvents.after_bulk_update`
NrL )rt r3 rL rL rM �after_bulk_deleteo rv z SessionEvents.after_bulk_deletec C rr )a� Intercept the "transient to pending" 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.
:param session: target :class:`.Session`
:param instance: the ORM-mapped instance being operated upon.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �transient_to_pending� rv z"SessionEvents.transient_to_pendingc C rr )a0 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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �pending_to_transient� rv z"SessionEvents.pending_to_transientc C rr )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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �persistent_to_transient� rv z%SessionEvents.persistent_to_transientc C rr )aN 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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �pending_to_persistent� rv z#SessionEvents.pending_to_persistentc C rr )a: 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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �detached_to_persistent� rv z$SessionEvents.detached_to_persistentc C rr )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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �loaded_as_persistent rv z"SessionEvents.loaded_as_persistentc C rr )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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �persistent_to_deleted0 rv z#SessionEvents.persistent_to_deletedc C rr )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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �deleted_to_persistentO rv z#SessionEvents.deleted_to_persistentc C rr )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`.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �deleted_to_detached_ rv z!SessionEvents.deleted_to_detachedc C rr )aD 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.
.. seealso::
:ref:`session_lifecycle_events`
NrL r' rL rL rM �persistent_to_detachedu rv z$SessionEvents.persistent_to_detachedN)rZ r rD r )r@ r rB rC rD r )
rO r r� rR r� rR rS r rD rT )r r. rD rT )r r r r/ rD rT )r r rD rT )r r r r/ rD rT )r r r� r0 r r rD rT )r r r� r0 rD rT )r r r r/ r� r1 rD rT )r r r& r* rD rT )r/ r* rD rT )r3 r* rD rT )&r{ r| r} r~ r r r� r
r� rN rk r r r r r r r r! r# r$ r% r( r) r! �_legacy_signaturer2 r4 r5 r6 r7 r8 r9 r: r; r< r= r> rL rL rL rM r st *
�
*
Q
+
(
$
!
�
$�
" " ! r c @ s� e Zd ZdZdZeZedFd d
��Ze dGdd��Z
e dHdIdd ��Z e d �dJd&d'�Z
e d �dKd(d)�Zd*d+�dLd0d1�Ze d �dKd2d3�ZdMd5d6�ZdNd9d:�ZdOd?d@�ZdPdBdC�ZdQdDdE�Zd*S )R�AttributeEventsa3 Define events for object attributes.
These are typically defined on the class-bound descriptor for the
target class.
For example, to register a listener that will receive the
:meth:`_orm.AttributeEvents.append` event::
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`, such as below,
illustrated using the :meth:`_orm.AttributeEvents.set` event::
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_attributerK � Type[_HasEventsDispatch[Any]]� dispatch_cls�Type[_Dispatch[Any]]rD �_Dispatch[Any]c C s t j�| |�}d|_|S )NF)r! r �
_set_dispatch�_active_history)rK rB ra rL rL rM rE � s z AttributeEvents._set_dispatchr@ �=Union[QueryableAttribute[Any], Type[QueryableAttribute[Any]]]rB rC c C s t |tj�rt|jj|j�S |S rF )rG r �MapperPropertyr` �parentrg rc rJ rL rL rM rN � s z AttributeEvents._accept_withFrO �"_EventKey[QueryableAttribute[Any]]�active_historyrR r� r� rQ � include_keyrT c s� |j |j}� |r
d|j_�r�r�s"d � ���fdd � }|�|�}|j|d
� |rMt�|j�} | � d�D ]}
|�
|
|j �jdd
� |rLd|
|j j_q5d S d S ) NTr@ r� rV r rS rD c s~ �s| � � } �s*|r|d }nd }�r � | g|�R i |�� |S � | g|�R � |S �r7� | g|�R i |��S � | g|�R � S �Nr )r� )r@ rV rS �value�rZ rL r� r� rL rM r�
s
�z%AttributeEvents._listen.<locals>.wrapr� )r@ r� rV r rS r rD r ) rd re ra rF ri rj r �manager_of_classrg r� rh rc ) rK rO rK r� r� rQ rL r@ r� r� r� rL rO rM rk � s$
���zAttributeEvents._listen)rc r* rN r+ � initiatorr, rc r- � Optional[_T]c C rr )aI 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.
:param key: When the event is established using the
:paramref:`.AttributeEvents.include_key` parameter set to
True, this will be the key used in the operation, such as
``collection[some_key_or_index] = value``.
The parameter is not passed
to the event at all if the the
:paramref:`.AttributeEvents.include_key`
was not used to set up the event; this is to allow backwards
compatibility with existing event handlers that don't include the
``key`` parameter.
.. versionadded:: 2.0
: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`
NrL �rt r@ rN rQ rc rL rL rM �append#
rv zAttributeEvents.appendc C rr )af Receive a collection append event where the collection was not
actually mutated.
This event differs from :meth:`_orm.AttributeEvents.append` in that
it is fired off for de-duplicating collections such as sets and
dictionaries, when the object already exists in the target collection.
The event does not have a return value and the identity of the
given object cannot be changed.
The event is used for cascading objects into a :class:`_orm.Session`
when the collection has already been mutated via a backref 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 that would be appended if the object did not
already exist in the collection.
: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.
:param key: When the event is established using the
:paramref:`.AttributeEvents.include_key` parameter set to
True, this will be the key used in the operation, such as
``collection[some_key_or_index] = value``.
The parameter is not passed
to the event at all if the the
:paramref:`.AttributeEvents.include_key`
was not used to set up the event; this is to allow backwards
compatibility with existing event handlers that don't include the
``key`` parameter.
.. versionadded:: 2.0
:return: No return value is defined for this event.
.. versionadded:: 1.4.15
NrL rS rL rL rM �append_wo_mutationV
rv z"AttributeEvents.append_wo_mutationN)�keysr� � Iterable[_T]rV �"Optional[Iterable[EventConstants]]c C rr )aR 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.
:param keys: When the event is established using the
:paramref:`.AttributeEvents.include_key` parameter set to
True, this will be the sequence of keys used in the operation,
typically only for a dictionary update. The parameter is not passed
to the event at all if the the
:paramref:`.AttributeEvents.include_key`
was not used to set up the event; this is to allow backwards
compatibility with existing event handlers that don't include the
``key`` parameter.
.. versionadded:: 2.0
.. seealso::
:class:`.AttributeEvents` - background on listener options such
as propagation to subclasses.
NrL )rt r@ r� rQ rV rL rL rM � bulk_replace�
rv z AttributeEvents.bulk_replacec C rr )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.
:param key: When the event is established using the
:paramref:`.AttributeEvents.include_key` parameter set to
True, this will be the key used in the operation, such as
``del collection[some_key_or_index]``. The parameter is not passed
to the event at all if the the
:paramref:`.AttributeEvents.include_key`
was not used to set up the event; this is to allow backwards
compatibility with existing event handlers that don't include the
``key`` parameter.
.. versionadded:: 2.0
:return: No return value is defined for this event.
.. seealso::
:class:`.AttributeEvents` - background on listener options such
as propagation to subclasses.
NrL rS rL rL rM rb �
rv zAttributeEvents.remove�oldvaluec C rr )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.
NrL )rt r@ rN rZ rQ rL rL rM �set�
rv zAttributeEvents.set�dict_�Dict[Any, Any]c C rr )a� 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.
: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::
:meth:`.AttributeEvents.init_collection` - collection version
of this event
:class:`.AttributeEvents` - background on listener options such
as propagation to subclasses.
:ref:`examples_instrumentation` - see the
``active_column_defaults.py`` example.
NrL )rt r@ rN r\ rL rL rM � init_scalar rv zAttributeEvents.init_scalarr� �Type[Collection[Any]]�collection_adapterr5 c C rr )aQ 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.
.. seealso::
:class:`.AttributeEvents` - background on listener options such
as propagation to subclasses.
:meth:`.AttributeEvents.init_scalar` - "scalar" version of this
event.
NrL �rt r@ r� r` rL rL rM �init_collection� rv z AttributeEvents.init_collection�Collection[Any]c C rr )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.
.. seealso::
:class:`.AttributeEvents` - background on listener options such
as propagation to subclasses.
NrL ra rL rL rM �dispose_collection� rv z"AttributeEvents.dispose_collectionc C rr )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.
NrL )rt r@ rQ rL rL rM �modified� rv zAttributeEvents.modified)rK rA rB rC rD rD )r@ rG rB rC rD rG )FFFFF)rO rJ rK rR r� rR r� rR rQ rR rL rR rD rT )
r@ r* rN r+ rQ r, rc r- rD rR )
r@ r* rN r+ rQ r, rc r- rD rT )
r@ r* r� rW rQ r, rV rX rD rT )
r@ r* rN r+ rZ r+ rQ r, rD rT )r@ r* rN r+ r\ r] rD rT )r@ r* r� r_ r` r5 rD rT )r@ r* r� rc r` r5 rD rT )r@ r* rQ r, rD rT )r{ r| r} r~ r r r� � staticmethodrE r� rN rk r rT rU rY rb r[ r^ rb rd re rL rL rL rM r@ � s8 E �7�9�7�N�
)
!
}
+ r@ c @ sJ e Zd ZdZdZeZd dd�Zd d d �Zd dd�Z e
d d dd��Z dS )!� QueryEventsa3 Represent events within the construction of a :class:`_query.Query`
object.
.. legacy:: The :class:`_orm.QueryEvents` event methods are legacy
as of SQLAlchemy 2.0, and only apply to direct use of the
:class:`_orm.Query` object. They are not used for :term:`2.0 style`
statements. For events to intercept and modify 2.0 style ORM use,
use the :meth:`_orm.SessionEvents.do_orm_execute` hook.
The :class:`_orm.QueryEvents` hooks are now superseded by the
:meth:`_orm.SessionEvents.do_orm_execute` event hook.
� SomeQueryr* �
Query[Any]rD rT c C rr )a# Receive the :class:`_query.Query`
object before it is composed into a
core :class:`_expression.Select` object.
.. deprecated:: 1.4 The :meth:`_orm.QueryEvents.before_compile` event
is superseded by the much more capable
:meth:`_orm.SessionEvents.do_orm_execute` hook. In version 1.4,
the :meth:`_orm.QueryEvents.before_compile` event is **no longer
used** for ORM-level attribute loads, such as loads of deferred
or expired attributes as well as relationship loaders. See the
new examples in :ref:`examples_session_orm_events` which
illustrate new ways of intercepting and modifying ORM queries
for the most common purpose of adding arbitrary filter criteria.
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`
NrL )rt r* rL rL rM �before_compile rv zQueryEvents.before_compiler/ r c C rr )a� Allow modifications to the :class:`_query.Query` object within
:meth:`_query.Query.update`.
.. deprecated:: 1.4 The :meth:`_orm.QueryEvents.before_compile_update`
event is superseded by the much more capable
:meth:`_orm.SessionEvents.do_orm_execute` hook.
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.datetime.now(
datetime.UTC
)
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`
NrL )rt r* r/ rL rL rM �before_compile_updateJ rv z!QueryEvents.before_compile_updater3 r c C rr )a] Allow modifications to the :class:`_query.Query` object within
:meth:`_query.Query.delete`.
.. deprecated:: 1.4 The :meth:`_orm.QueryEvents.before_compile_delete`
event is superseded by the much more capable
:meth:`_orm.SessionEvents.do_orm_execute` hook.
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`
NrL )rt r* r3 rL rL rM �before_compile_delete� rv z!QueryEvents.before_compile_deleteFrO r� r� rR �bake_okrS r c sX |j � �sd� �fdd� }|�|�}n d� fdd� }|�|�}||_|jd i |�� d S )
NrV r rS rD c s, �s| d }� | i |�� |S � | i |��S rM rL )rV rS r* �rZ r� rL rM r� � s
z!QueryEvents._listen.<locals>.wrapc s � | i |��S rF rL r� r rL rM r� � s r� rL )re ri �_bake_okrj )rK rO r� rm rS r� rL rn rM rk � s
zQueryEvents._listenN)r* ri rD rT )r* ri r/ r rD rT )r* ri r3 r rD rT )FF)
rO r� r� rR rm rR rS r rD rT ) r{ r| r} r~ r r r� rj rk rl r� rk rL rL rL rM rg � s
A
6)�rg )\r~ �
__future__r �typingr r r r r r r r
r r r
r r rf � r r r �
attributesr �baser r r r r* r r r �scopingr r r r r! r" r# r$ �event.registryr% � util.compatr& r' �_typingr( r) r* r+ r, r- r. r/ �
unitofworkr0 �enginer1 �
event.baser2 r3 r4 �orm.collectionsr5 � orm.contextr6 � orm.decl_apir7 r8 �
orm.mapperr9 � orm.stater: r; r= r r> rI r� �
RefCollectionr� r� r� r� r[ r r� r r@ rg rL rL rL rM �<module> s� s 5_ f