_rollback_exceptionr? ResourceClosedError)rM prepared_ok rollback_ok deactive_ok
closed_msgs r" _assert_activez!SessionTransaction._assert_active s, ;) # #,>
[H
$
$
0B
[H
$
$
{
+ 46
2 3 $ % 4F
[F
"
",Z88 8 #
"r* c | j p| j S rS )rE rD rQ s r" _is_transaction_boundaryz+SessionTransaction._is_transaction_boundary3 s {.$, ..r* c | | | j j |fi |}| || S rS )r_ rB get_bind_connection_for_bind)rM bindkeyexecution_optionsr/ binds r"
connectionz SessionTransaction.connection7 sG $t|$W7777((/@AAAr* c X | t | j | | S )NrE )r_ r rB )rM rE s r" _beginzSessionTransaction._begin< s+ !$,VDDDDr* c | }d}|r7||fz
}|j |u rn'|j t j d|z |j }|7|S )Nr: z4Transaction %s is not on the active transaction list)rD rG rH )rM uptocurrentresults r" _iterate_self_and_parentsz,SessionTransaction._iterate_self_and_parents@ sr
* wj F$&& ( 0J
"/
*
r* c | j sF| j j | _ | j j | _ | j j | _ | j j | _ d S | j j s| j t j
| _ t j
| _ t j
| _ t j
| _ d S rS ) ra rD _new_deleted_dirty
_key_switchesrB _flushingflushweakrefWeakKeyDictionaryrQ s r" rJ z!SessionTransaction._take_snapshotR s , )DI L 1DM ,-DK!% !;D F|% ! L -// 133
/11 $ 6 8 8r* c | j sJ t | j | j j }| j |d | j D ]Q\ }\ }}| j j | ||_
||vr | j j | Rt | j | j j D ] }| j
|d | j j rJ | j j D ]>}|r|j s || j v r*| |j | j j j ?dS )zmRestore the restoration state taken before a transaction began.
Corresponds to a rollback.
T to_transient)revert_deletionN)ra setrr unionrB _expunge_statesru items identity_map safe_discardkeyreplacers _update_impl
all_statesmodifiedrt _expiredict _modified)rM
dirty_only
to_expungesoldkeynewkeys r" _restore_snapshotz$SessionTransaction._restore_snapshotb s ,,,,^^))$,*;<<
$$Zd$CCC#'#5#;#;#=#=
5
5 A
L % 2 21 5 5 5 AE
"" )11!444T]##))$,*?@@ ? ?A L % %a % > > > ><(((( *5577 G GA
G
GqDK/?/? !&$,";"EFFF G Gr* c | j sJ | j s| j j r| j j D ],}| |j | j j j -t j
t | j
| j | j
dS | j r| j j | j | j j | j | j j
| j
| j j | j dS dS )zjRemove the restoration state taken before a transaction began.
Corresponds to a commit.
N)ra rE rB expire_on_commitr r r r r statelib
InstanceState_detach_stateslistrs clearrD rr updatert ru )rM r s r" _remove_snapshotz#SessionTransaction._remove_snapshot s@ ,,,,{ Bt| < B\.99;;
G
G !&$,";"EFFFF " 1 1T]##T\
M ! ! ! ! !
[ B L $ $TY / / / L & &t{ 3 3 3 L ! ( ( 7 7 7 L & - -d.@ A A A A A B Br* c ( | || j v r)|rt j d | j | d S d}| j r%| j || }| j s|S nUt |t j r%|}|j | j v rt j d n| }d} |r
|j
di |}| j j r | j | }n0| j r| }n| }||||ufx| j |< | j |j < | j j | j | | |S # |r| xY w)NzOConnection is already established for the given bind; execution_options ignoredr FzMSession already has a Connection associated for the given Connection's EngineTr: )r_ rC r warnrD rd rE
isinstancer
ConnectionrG rH _contextual_connectrf rB twophasebegin_twophase begin_nestedbeginrK after_beginclose)rM rg rf
local_connectconn transactions r" rd z'SessionTransaction._connection_for_bind s 4$ $ $
< $T*1- -
< %<44T;LMMD;
$ 122
%;$"333 44 4 //11 $
C-t-BB0ABB|$
+ )= " 1 1 3 3
+ " / / 1 1 "jjll D H
D d #d&7 &D
L ! - -dlD$ G G GK
s
A'E8 8Fc | | j | j j st j d | d S )NzD'twophase' mode not enabled, or not root transaction; can't prepare.)rD rB r rG rH
_prepare_implrQ s r" preparezSessionTransaction.prepare sH < #4<+@ #,!
r* c , | | j | j r$| j j | j | j j }|| ur-| | D ]}| | j j sZt d D ]6}| j r n.| j 7t j d | j | j j r t! | j D ] }|d nF# t) j 5 | d d d n # 1 swxY w Y Y nxY wt. | _ d S )Nrm d zrOver 100 subsequent flushes have occurred within session.commit() - is an after_flush() hook creating new objects?r )r_ rD rE rB rK
before_commitr rp commitrv range _is_cleanrw r
FlushErrorr r~ rC valuesr r safe_reraiserollbackr< rF )rM stxsubtransaction _flush_guardts r" r z SessionTransaction._prepare_impl s < 4; L ! / / = = =l& d??"%"?"?T"?"J"J
(
( %%''''|%
%c
<))++ E ""$$$$n, < DL$9
$ T . 5 5 7 788 # #AaDLLNNNN#
$&(( $ $MMOOO$ $ $ $ $ $ $ $ $ $ $ $ $ $ $ s1 >AE FE8, F8E< <F?E< Fc | d | j t ur| | j | j rt
| j D ] }|d t | _ | j j
| j | j j r| | | j S )NT)r[ r )r_ rF r< r rD rE r~ rC r r r= rB rK after_commitrI r r )rM r s r" r zSessionTransaction.commit s --- ;h & & < 4; *113344
!
#DK L ! . .t| < < <|:
(%%'''
|r* c | dd | j j }|| ur-| | D ]}| | }d }| j t t fv r4| D ] }|j |j r t |j D ] }|d
t |_ | j j | j n# t# j }Y nxY wt |_ | j j r| |j n9# t |_ | j j r | |j w w xY w|} nt |_ | j }|sJ|j rC| s/t- j d | |j | | j r%|r#t# j d | j _ |r"t- j |d |d |j || | j S ) NT)r[ r\ r r )r z\Session's state has been changed on a non-active transaction - this state will be discarded.r with_traceback)r_ rB r rp r rF r; r< rD rE r~ rC r r r> rK after_rollbacksysexc_inforI r r r r rY raise_after_soft_rollback) rM _capture_exceptionr r boundary rollback_errr r sesss r" r zSessionTransaction.rollback s $???l& d??"%"?"?T"?"J"J
'
' $$&&&& ;68, , , # = = ? ?
2
2 &.+2D.
!$[%=%D%D%F%F!G!G , ,A aDMMOOOO-5 * -< | dd | j j d S |a | d S # t j 5 | d d d n# 1 swxY w Y Y d S Y d S xY w| d S )NT)r] r[ )r_ rB r r r r r )rM type_value tracebacks r" __exit__zSessionTransaction.__exit__] s $??? < # + F =
$
$&(( $ $MMOOO$ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $
MMOOOOOs- ? BA5) B5A9 9B<A9 =B)NF)FFFrU rS F)r3 r4 r5 r6 rY rO propertyrN rE rT r_ ra rh rk rp rJ r r rd r r r r r r r r: r* r" r r e s s sj K K K K" X " F B B XB
/ %9 %9 %9 %9N / / X/B B B B
E E E E $9 9 9 G G G G@B B B,3 3 3j @ $; ; ; ; z! ! ! !, r* r c $ e Zd ZdZdZ ej ddd dNd
ZdZdZ ej
d Z dOd Z d
Z
d Zd Zd Z dPdZdQdZdRdZdRdZd Zd Zd Zd Zd Zd Zd ZdSd Z d Z e ej d Z d Z! dRd Z"d! Z#dQd"Z$d# Z%d$ Z& ej' d%d& d' Z(d( Z)dTd)Z*d* Z+d+ Z,d, Z-dUd-Z.d. Z/d/ Z0d0 Z1d1 Z2dUd2Z3 dVd3Z4d4 Z5d5 Z6dTd6Z7d7 Z8d8 Z9d9 Z:d: Z;d; ZdQd>Z?d? Z@d@ ZAdQdAZB dWdBZC dOdCZDdD ZEdE ZF ej dFG dXdH ZGe dI ZHdZI e dJ ZJe dK ZKe dL ZLe dM ZMdS )Yr zManages persistence operations for ORM-mapped objects.
The Session's usage paradigm is described at :doc:`/orm/session`.
) __contains____iter__addadd_allr r r r rh deleteexecuteexpire
expire_allexpunge expunge_allrw rc is_modifiedbulk_save_objectsbulk_insert_mappingsbulk_update_mappingsmerger refreshr scalar)z1.0a The :paramref:`.Session.weak_identity_map` parameter as well as the strong-referencing identity map are deprecated, and will be removed in a future release. For the use case where objects present in a :class:`.Session` need to be automatically strong referenced, see the recipe at :ref:`session_referencing_behavior` for an event-based approach to maintaining strong identity references. )0.7zxThe :paramref:`.Session._enable_transaction_accounting` parameter is deprecated and will be removed in a future release.)r z:class:`.SessionExtension` is deprecated in favor of the :class:`.SessionEvents` listener interface. The :paramref:`.Session.extension` parameter will be removed in a future release.)weak_identity_maprI extensionNTFc
|dv rt j | _ nt j | _ | | _ i | _ i | _ || _ i | _ d| _ d| _
d| _ t | _
|| _ || _ || _ |
| _ || _ || _ | r| n t( j | _ | r| j | | r,t3 j | D ]}
t7 j | |
|0| D ]\ }}| || | j s| | t@ | j
< dS )a Construct a new Session.
See also the :class:`.sessionmaker` function which is used to
generate a :class:`.Session`-producing callable with a given
set of arguments.
:param autocommit:
.. warning::
The autocommit flag is **not for general use**, and if it is
used, queries should only be invoked within the span of a
:meth:`.Session.begin` / :meth:`.Session.commit` pair. Executing
queries outside of a demarcated transaction is a legacy mode
of usage, and can in some cases lead to concurrent connection
checkouts.
Defaults to ``False``. When ``True``, the
:class:`.Session` does not keep a persistent transaction running,
and will acquire connections from the engine on an as-needed basis,
returning them immediately after their use. Flushes will begin and
commit (or possibly rollback) their own transaction if no
transaction is present. When using this mode, the
:meth:`.Session.begin` method is used to explicitly start
transactions.
.. seealso::
:ref:`session_autocommit`
:param autoflush: When ``True``, all query operations will issue a
:meth:`~.Session.flush` call to this ``Session`` before proceeding.
This is a convenience feature so that :meth:`~.Session.flush` need
not be called repeatedly in order for database queries to retrieve
results. It's typical that ``autoflush`` is used in conjunction
with ``autocommit=False``. In this scenario, explicit calls to
:meth:`~.Session.flush` are rarely needed; you usually only need to
call :meth:`~.Session.commit` (which flushes) to finalize changes.
:param bind: An optional :class:`_engine.Engine` or
:class:`_engine.Connection` to
which this ``Session`` should be bound. When specified, all SQL
operations performed by this session will execute via this
connectable.
:param binds: A dictionary which may specify any number of
:class:`_engine.Engine` or :class:`_engine.Connection`
objects as the source of
connectivity for SQL operations on a per-entity basis. The keys
of the dictionary consist of any series of mapped classes,
arbitrary Python classes that are bases for mapped classes,
:class:`_schema.Table` objects and :class:`_orm.Mapper` objects.
The
values of the dictionary are then instances of
:class:`_engine.Engine`
or less commonly :class:`_engine.Connection` objects.
Operations which
proceed relative to a particular mapped class will consult this
dictionary for the closest matching entity in order to determine
which :class:`_engine.Engine` should be used for a particular SQL
operation. The complete heuristics for resolution are
described at :meth:`.Session.get_bind`. Usage looks like::
Session = sessionmaker(binds={
SomeMappedClass: create_engine('postgresql://engine1'),
SomeDeclarativeBase: create_engine('postgresql://engine2'),
some_mapper: create_engine('postgresql://engine3'),
some_table: create_engine('postgresql://engine4'),
})
.. seealso::
:ref:`session_partitioning`
:meth:`.Session.bind_mapper`
:meth:`.Session.bind_table`
:meth:`.Session.get_bind`
:param \class_: Specify an alternate class other than
``sqlalchemy.orm.session.Session`` which should be used by the
returned class. This is the only argument that is local to the
:class:`.sessionmaker` function, and is not sent directly to the
constructor for ``Session``.
:param enable_baked_queries: defaults to ``True``. A flag consumed
by the :mod:`sqlalchemy.ext.baked` extension to determine if
"baked queries" should be cached, as is the normal operation
of this extension. When set to ``False``, all caching is disabled,
including baked queries defined by the calling application as
well as those used internally. Setting this flag to ``False``
can significantly reduce memory use, however will also degrade
performance for those areas that make use of baked queries
(such as relationship loaders). Additionally, baked query
logic in the calling application or potentially within the ORM
that may be malfunctioning due to cache key collisions or similar
can be flagged by observing if this flag resolves the issue.
.. versionadded:: 1.2
:param _enable_transaction_accounting: A
legacy-only flag which when ``False`` disables *all* 0.5-style
object accounting on transaction boundaries.
:param expire_on_commit: Defaults to ``True``. When ``True``, all
instances will be fully expired after each :meth:`~.commit`,
so that all attribute/object access subsequent to a completed
transaction will load from the most recent database state.
.. seealso::
:ref:`session_committing`
:param extension: An optional
:class:`~.SessionExtension` instance, or a list
of such instances, which will receive pre- and post- commit and
flush events, as well as a post-rollback event.
:param info: optional dictionary of arbitrary data to be associated
with this :class:`.Session`. Is available via the
:attr:`.Session.info` attribute. Note the dictionary is copied at
construction time so that modifications to the per-
:class:`.Session` dictionary will be local to that
:class:`.Session`.
.. versionadded:: 0.9.0
:param query_cls: Class which should be used to create new Query
objects, as returned by the :meth:`~.Session.query` method.
Defaults to :class:`_query.Query`.
:param twophase: When ``True``, all transactions will be started as
a "two phase" transaction, i.e. using the "two phase" semantics
of the database in use along with an XID. During a
:meth:`~.commit`, after :meth:`~.flush` has been issued for all
attached databases, the :meth:`~.TwoPhaseTransaction.prepare`
method on each database's :class:`.TwoPhaseTransaction` will be
called. This allows each database to roll back the entire
transaction, before each transaction is committed.
:param weak_identity_map: Defaults to ``True`` - when set to
``False``, objects placed in the :class:`.Session` will be
strongly referenced until explicitly removed or the
:class:`.Session` is closed.
TNFN)!r WeakInstanceDict
_identity_clsStrongInstanceDictr rr rs rg _Session__bindsrv _warn_on_eventsr _new_sessionidhash_key autoflushr r enable_baked_queriesrI r r Query
_query_clsinfor r to_listr _adapt_listenerr _add_bindr r )rM rg r r rI r r r bindsr r r query_clsextr s r" rO zSession.__init__ sr z , ,!)!:D !)! Close this Session.
This clears all items and ends any transaction in progress.
If this session were created with ``autocommit=False``, a new
transaction is immediately begun. Note that this new transaction does
not use any connection resources until they are first needed.
Fr N _close_implrQ s r" r z
Session.close s!
E*****r* c 2 | d dS )a Close this Session, using connection invalidation.
This is a variant of :meth:`.Session.close` that will additionally
ensure that the :meth:`_engine.Connection.invalidate`
method will be called
on all :class:`_engine.Connection` objects. This can be called when
the database is known to be in a state where the connections are
no longer safe to be used.
E.g.::
try:
sess = Session()
sess.add(User())
sess.commit()
except gevent.Timeout:
sess.invalidate()
raise
except:
sess.rollback()
raise
This clears all items and ends any transaction in progress.
If this session were created with ``autocommit=False``, a new
transaction is immediately begun. Note that this new transaction does
not use any connection resources until they are first needed.
.. versionadded:: 0.9.9
Tr Nr rQ s r" r zSession.invalidate& s" @
D)))))r* c | | j 1| j D ]}| | d S d S rS )r r rp r )rM r r s r" r zSession._close_implH sd ' # / I I K K
.
. !!*---- ( '
.
.r* c | j t | j z }| | _ i | _ i | _ t j || dS )zRemove all object instances from this ``Session``.
This is equivalent to calling ``expunge(obj)`` on all objects in this
``Session``.
N) r r r rr r rs r r r )rM r s r" r zSession.expunge_allN sf &1133d49ooE
. . 0 0
--j$?????r* c t | }|j r || j |< d S |j r%|| j |j < |j D ] }|| j |<
d S t
j d|z # t j $ r\}t |t s,t j t
j d|z | n|| j |< Y d }~d S Y d }~d S d }~ww xY w)Nz!Not an acceptable bind target: %sreplace_context)
r
is_selectabler is_mapperclass_ _all_tablesrG
ArgumentErrorNoInspectionAvailabler typer r )rM r rg insp
selectableerrs r" r zSession._add_bind] sB 3< # 6F!!-f4HHH / /ADL(( #|A... ) 9 9 fcn : ; ; ; 2f/4 2,1 1 NN;/ 0 0 0 NN+ , , ,* Fyy!!
#
s A B?BBc | j || fi |S )zZReturn a new :class:`_query.Query` object corresponding to this
:class:`.Session`.)r )rM entitiesr/ s r" r z
Session.query1 s tx88888r* c # V K | j }d| _ | V || _ dS # || _ w xY w)ag Return a context manager that disables autoflush.
e.g.::
with session.no_autoflush:
some_object = SomeClass()
session.add(some_object)
# won't autoflush
some_object.related_thing = session.query(SomeRelated).first()
Operations that proceed within the ``with:`` block
will not be subject to flushes occurring upon query
access. This is useful when initializing a series
of objects which involve existing database queries,
where the uncompleted object should not yet be flushed.
FN)r )rM r s r" no_autoflushzSession.no_autoflush7 sB * N 'JJJ &DNNNYDN & & & &s (c | j r}| j sx | d S # t j $ rM}| d t
j |t j d Y d }~d S d }~ww xY wd S d S )Nzraised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurelyr r )
r rv rw rG StatementError
add_detailr r r r )rM es r"
_autoflushzSession._autoflushS s >
A$.
A
A
(
A
A
A
5
AclnnQ.?@@@@@@@@@@
A
A
A
A
As & BAA==Bc t j | }nD# t j $ r2}t j t j | | Y d}~nd}~ww xY w| || |i k rt j d |r t j | }n0|.|du rt j }n|rt j di |}nd}t j |
t | |j ||| $t j dt% | z dS )a{ Expire and refresh the attributes on the given instance.
A query will be issued to the database and all attributes will be
refreshed with their current database value.
Lazy-loaded relational attributes will remain lazily loaded, so that
the instance-wide refresh operation will be followed immediately by
the lazy load of that attribute.
Eagerly-loaded relational attributes will eagerly load within the
single refresh operation.
Note that a highly isolated transaction will return the same values as
were previously read in that same transaction, regardless of changes
in database state outside of that transaction - usage of
:meth:`~Session.refresh` usually only makes sense if non-ORM SQL
statement were emitted in the ongoing transaction, or if autocommit
mode is turned on.
:param attribute_names: optional. An iterable collection of
string attribute names indicating a subset of attributes to
be refreshed.
:param with_for_update: optional boolean ``True`` indicating FOR UPDATE
should be used, or may be a dictionary containing flags to
indicate a more specific set of FOR UPDATE flags for the SELECT;
flags should match the parameters of
:meth:`_query.Query.with_for_update`.
Supersedes the :paramref:`.Session.refresh.lockmode` parameter.
.. versionadded:: 1.2
:param lockmode: Passed to the :class:`~sqlalchemy.orm.query.Query`
as used by :meth:`~sqlalchemy.orm.query.Query.with_lockmode`.
Superseded by :paramref:`.Session.refresh.with_for_update`.
.. seealso::
:ref:`session_expire` - introductory material
:meth:`.Session.expire`
:meth:`.Session.expire_all`
:meth:`_orm.Query.populate_existing`
r Nzqwith_for_update should be the boolean value True, or a dictionary with options. A blank dictionary is ambiguous.T)
refresh_statewith_for_updateonly_load_propsz Could not refresh instance '%s'r: )r instance_stater NO_STATEr r UnmappedInstanceError
_expire_staterG r" r LockmodeArgparse_legacy_queryr
load_on_identr r rH r )rM r2 attribute_namesrF lockmoder r' s r" r zSession.refreshc s l -h77EE| K)(33 #
5/222 b &3
' # / B B8 L LOO
( $&&"'"3"5"5
'"'"3"F"Fo"F"F"&
!
=2233 # / /
,1L4J4JJ
A(AAc | j D ]'}| |j | j j (dS )a Expires all persistent instances within this Session.
When any attributes on a persistent instance is next accessed,
a query will be issued using the
:class:`.Session` object's current transactional context in order to
load all expired attributes for the given instance. Note that
a highly isolated transaction will return the same values as were
previously read in that same transaction, regardless of changes
in database state outside of that transaction.
To expire individual objects and individual attributes
on those objects, use :meth:`Session.expire`.
The :class:`.Session` object's default behavior is to
expire all state whenever the :meth:`Session.rollback`
or :meth:`Session.commit` methods are called, so that new
state can be loaded for the new transaction. For this reason,
calling :meth:`Session.expire_all` should not be needed when
autocommit is ``False``, assuming the transaction is isolated.
.. seealso::
:ref:`session_expire` - introductory material
:meth:`.Session.expire`
:meth:`.Session.refresh`
:meth:`_orm.Query.populate_existing`
N)r r r r r rM r s r" r zSession.expire_all sP @ &1133 C CE MM%*d&7&A B B B B C Cr* c t j | }nD# t j $ r2}t j t j | | Y d}~nd}~ww xY w| || dS )a Expire the attributes on an instance.
Marks the attributes of an instance as out of date. When an expired
attribute is next accessed, a query will be issued to the
:class:`.Session` object's current transactional context in order to
load all expired attributes for the given instance. Note that
a highly isolated transaction will return the same values as were
previously read in that same transaction, regardless of changes
in database state outside of that transaction.
To expire all objects in the :class:`.Session` simultaneously,
use :meth:`Session.expire_all`.
The :class:`.Session` object's default behavior is to
expire all state whenever the :meth:`Session.rollback`
or :meth:`Session.commit` methods are called, so that new
state can be loaded for the new transaction. For this reason,
calling :meth:`Session.expire` only makes sense for the specific
case that a non-ORM SQL statement was emitted in the current
transaction.
:param instance: The instance to be refreshed.
:param attribute_names: optional list of string attribute names
indicating a subset of attributes to be expired.
.. seealso::
:ref:`session_expire` - introductory material
:meth:`.Session.expire`
:meth:`.Session.refresh`
:meth:`_orm.Query.populate_existing`
r N)r rH r rI r r rJ rK )rM r2 rO r r' s r" r zSession.expire s J -h77EE| K)(33 #
5/22222rQ c 0 | | |r | |j | d S t |j j d| }| | |D ] \ }}}}| | d S )Nzrefresh-expire)_validate_persistent_expire_attributesr r managerr cascade_iterator_conditional_expire)rM r rO cascadedomst_dct_s r" rK zSession._expire_state s !!%(((
. $ $UZ A A A A A
$556FNN H
$ $U + + +#+
.
.1c4((----
.
.r* c |j r'| |j | j j dS || j v r1| j | | | dS dS )z5Expire a state if persistent, else expunge if pendingN)r r r r r rr pop_detachrS s r" rZ zSession._conditional_expire! sq 9 MM%*d&7&A B B B B B
di
IMM% MM$
r* r zThe :meth:`.Session.prune` method is deprecated along with :paramref:`.Session.weak_identity_map`. This method will be removed in a future release.c 4 | j S )a Remove unreferenced instances cached in the identity map.
Note that this method is only meaningful if "weak_identity_map" is set
to False. The default weak identity map is self-pruning.
Removes any object in this Session's identity map that is not
referenced in user code, modified, new or scheduled for deletion.
Returns the number of objects pruned.
)r prunerQ s r" rd z
Session.prune* s " &&(((r* c t j | }nD# t j $ r2}t j t j | | Y d}~nd}~ww xY w|j | j ur$t j
dt | z t |j
j d| }| |gd |D z dS )zRemove the `instance` from this ``Session``.
This will free all internal references to the instance. Cascading
will be applied according to the *expunge* cascade rule.
r Nz*Instance %s is not present in this Sessionr c g | ] \ }}}}|
S r: r: ).0r\ r] r^ r_ s r"
z#Session.expunge..S s 'L'L'L1c4'L'L'Lr* )r rH r rI r r rJ r r rG rH r r rX r rY r )rM r2 r r' r[ s r" r zSession.expunge= s -h77EE| K)(33 #
4= 0 0,z/Session._register_persistent.. s) 5 5UeUZ
5 5 5 5 5 5r* ) rK pending_to_persistentr obj_identity_key_from_stater
intersectionallow_partial_pks
issupersetr r r r r r r ru r r r _orphaned_outside_of_sessionr r _commit_all_states_register_alteredrr r~ ra ) rM rk rq r r rr instance_keyorig_keyolds r" _register_persistentz Session._register_persistentd s !%
C Kt 9 ; 9 ;E"5))F ))++C % > >u E E *<?;; " 4 !+LO<<
.? $E**+ 9$ ,EIIY,.. %225999 0 >>>#'#3#A%#H#K#(9 $=D$259 !-EI
'//66O 77<< LL -II 0<||> 6;2 11 5 5f 5 5 5t7H
v&&& , ,,TY77
3
3%%dE2222 [[--di88 ! !E IMM% ! !r* c | j r4| j r/|D ].}|| j v rd| j j |< d| j j |< +d S d S d S NT)rI r rr rt )rM rk r s r" ry zSession._register_altered sw . :43C :
:
:DI%%37D$)%0059D$+E22 : : : :
:
:r* c & | j j pd }|D ]}| j r| j rd| j j |< || }| j | | j |d d|_ | || | d S r ) rK persistent_to_deletedrI r rs rr r r ra )rM rk r r rr s r" _remove_newly_deletedz Session._remove_newly_deleted s $
C Kt 3 3E2
8t7G
837 )%0$0 iikk * *5 1 1 1 M eT * * * !EN %0%%dE222! 3 3r* c |r | j r| d t j | }nD# t j $ r2}t
j t j | | Y d}~nd}~ww xY w| | dS )zPlace an object in the ``Session``.
Its state will be persisted to the database on the next flush
operation.
Repeated calls to ``add()`` will be ignored. The opposite of ``add()``
is ``expunge()``.
z
Session.add()r N)
r _flush_warningr rH r rI r r rJ _save_or_update_state)rM r2 _warnr r' s r" r z Session.add s 1T) 1 0 0 0 -h77EE| K)(33 #
""5)))))s 5 A6(A11A6c v | j r| d |D ]}| |d dS )z:Add the given collection of instances to this ``Session``.zSession.add_all()F)r N)r r r )rM instancesr2 s r" r zSession.add_all sV 5 3 4 4 4! , ,H HHXUH + + + + , ,r* c d|_ | | t | }| d|| j D ] \ }}}}| | d S )NFz save-update)halt_on)rw _save_or_update_implr rY _contains_state)rM r r r\ r] r^ r_ s r" r z Session._save_or_update_state s -2* !!%((( u%% % 6 6 5$*> 7
+ +OAq#t
% %c * * * * + +r* c " | j r| d t j | }nD# t j $ r2}t
j t j | | Y d}~nd}~ww xY w| ||d dS )zfMark an instance as deleted.
The database delete operation occurs upon ``flush()``.
zSession.delete()r NT)head)
r r r rH r rI r r rJ _delete_implrM r2 r r' s r" r zSession.delete s 4 2 3 3 3 -h77EE| K)(33 #
%55555s 3 A4(A//A4c |j (|r$t j dt | z d S | || }|| j v rd S | j | |r| || |r-t |j
j d| }|| j |< |r!|D ] \ }}}} |
||d d S d S )N Instance '%s' is not persistedr F)r rG rH r _before_attachrs r r
_after_attachr rX r rY r )
rM r rr r to_attachcascade_statesr\ r] r^ r_ s
r" r zSession._delete_impl s' 9
04y7G7GG ''s33 DM ! ! F e$$$ + uc * * * "
$55hFF N #
e 1#1
1
11c4!!#q%0000 1 1
1
1r* c L | j r| d i }i }|r| t | | j } d| _ | t
j | t
j | ||| || _ S # || _ w xY w)a
Copy the state of a given instance into a corresponding instance
within this :class:`.Session`.
:meth:`.Session.merge` examines the primary key attributes of the
source instance, and attempts to reconcile it with an instance of the
same primary key in the session. If not found locally, it attempts
to load the object from the database based on primary key, and if
none can be located, creates a new instance. The state of each
attribute on the source instance is then copied to the target
instance. The resulting target instance is then returned by the
method; the original source instance is left unmodified, and
un-associated with the :class:`.Session` if not already.
This operation cascades to associated instances if the association is
mapped with ``cascade="merge"``.
See :ref:`unitofwork_merging` for a detailed discussion of merging.
.. versionchanged:: 1.1 - :meth:`.Session.merge` will now reconcile
pending objects with overlapping primary keys in the same way
as persistent. See :ref:`change_3601` for discussion.
:param instance: Instance to be merged.
:param load: Boolean, when False, :meth:`.merge` switches into
a "high performance" mode which causes it to forego emitting history
events as well as all database access. This flag is used for
cases such as transferring graphs of objects into a :class:`.Session`
from a second level cache, or to transfer just-loaded objects
into the :class:`.Session` owned by a worker thread or process
without re-querying the database.
The ``load=False`` use case adds the caveat that the given
object has to be in a "clean" state, that is, has no pending changes
to be flushed - even if the incoming object is detached from any
:class:`.Session`. This is so that when
the merge operation populates local attributes and
cascades to related objects and
collections, the values can be "stamped" onto the
target object as is, without generating any history or attribute
events, and without the need to reconcile the incoming data with
any existing related objects or collections that might not
be loaded. The resulting objects from ``load=False`` are always
produced as "clean", so it is only appropriate that the given objects
should be "clean" as well, else this suggests a mis-use of the
method.
.. seealso::
:func:`.make_transient_to_detached` - provides for an alternative
means of "merging" a single object into the :class:`.Session`
zSession.merge()F)load
_recursive_resolve_conflict_map) r r rC r r _merger rH
instance_dict)rM r2 r r r r s r" r z
Session.merge1 s n 3 1 2 2 2
" OO h N
' "DN;;)(33(22%&; 'DNNYDN & & & &s
AB B#c t | }||v r|| S d}|j }||| j v r$t j dt | z |st
j d | | }t j
|d vo
?S,A%A%A.s3
?> 4K
-::<< ) 8 @ @ #& !!,/// # "
? FM2266s1v>> >)6688F%4V<
FNN 0. 1:%0@0@A iikk ; F''s33
%&&& ) % %e , , , , ! !% ( ( ( = uc * * * * *
= M / /e < < < < < = =r* c l |j | | d S | | d S rS )r r r rS s r" r z Session._save_or_update_implQ s< 9 OOE " " " " " e $ $ $ $ $r* c t j | }| || }d|_ |r| || dS dS )a
Associate an object with this :class:`.Session` for related
object loading.
.. warning::
:meth:`.enable_relationship_loading` exists to serve special
use cases and is not recommended for general use.
Accesses of attributes mapped with :func:`_orm.relationship`
will attempt to load a value from the database using this
:class:`.Session` as the source of connectivity. The values
will be loaded based on foreign key and primary key values
present on this object - if not present, then those relationships
will be unavailable.
The object will be attached to this session, but will
**not** participate in any persistence operations; its state
for almost all purposes will remain either "transient" or
"detached", except for the case of relationship loading.
Also note that backrefs will often not work as expected.
Altering a relationship-bound attribute on the target object
may not fire off a backref event, if the effective value
is what was already loaded from a foreign-key-holding value.
The :meth:`.Session.enable_relationship_loading` method is
similar to the ``load_on_pending`` flag on :func:`_orm.relationship`.
Unlike that flag, :meth:`.Session.enable_relationship_loading` allows
an object to remain transient while still being able to load
related items.
To make a transient object associated with a :class:`.Session`
via :meth:`.Session.enable_relationship_loading` pending, add
it to the :class:`.Session` using :meth:`.Session.add` normally.
If the object instead represents an existing identity in the database,
it should be merged using :meth:`.Session.merge`.
:meth:`.Session.enable_relationship_loading` does not improve
behavior when the ORM is used normally - object references should be
constructed at the object level, not at the foreign key level, so
that they are present in an ordinary way before flush()
proceeds. This method is not intended for general use.
.. seealso::
:paramref:`_orm.relationship.load_on_pending` - this flag
allows per-relationship loading of many-to-ones on items that
are pending.
:func:`.make_transient_to_detached` - allows for an object to
be added to a :class:`.Session` without SQL emitted, which then
will unexpire attributes on access.
TN)r rH r
_load_pendingr )rM rr r r s r" enable_relationship_loadingz#Session.enable_relationship_loadingW s` n )#..''s33 " + uc * * * * * + +r* c |j | j k rdS |j rC|j t v r5t j dt | d|j d| j d | j | | dS )NFzObject 'z"' is already attached to session 'z ' (this is 'z')T)r r r rG rH r rK
before_attachrM r rr s r" r zSession._before_attach s t} , ,5 0I = =,, U####U%5%5%5t}}}F
##D%000tr* c | j |_ |j r|j ||_ | j | | |j r | j | | d S | j | | d S rS ) r r r _strong_objrK after_attachr detached_to_persistenttransient_to_pendingr s r" r zSession._after_attach s = > $e / 7 #E
""4/// 9 < M 0 0u = = = = = M . .tU ; ; ; ; ;r* c t j | }nD# t j $ r2}t j t j | | Y d}~nd}~ww xY w| | S )zReturn True if the instance is associated with this session.
The instance may be pending or persistent within the Session for a
result of True.
r N)r rH r rI r r rJ r r s r" r zSession.__contains__ s -h77EE| K)(33 #
##E***rQ c t t | j t | j z S )zWIterate over all pending or persistent instances within this
Session.
)iterr rr r r rQ s r" r zSession.__iter__ sK
!!## $ $tD,=,D,D,F,F'G'G G
r* c H || j v p| j | S rS )rr r rj rS s r" r zSession._contains_state s% !LT%6%E%Ee%L%LLr* c | j rt j d | rdS d| _ | | d| _ dS # d| _ w xY w)a Flush all the object changes to the database.
Writes out all pending object creations, deletions and modifications
to the database as INSERTs, DELETEs, UPDATEs, etc. Operations are
automatically ordered by the Session's unit of work dependency
solver.
Database operations will be issued in the current transactional
context and do not affect the state of the transaction, unless an
error occurs, in which case the entire transaction is rolled back.
You may flush() as often as you like within a transaction to move
changes from Python to the database's transaction buffer.
For ``autocommit`` Sessions with no active manual transaction, flush()
will create a transaction on the fly that surrounds the entire set of
operations into the flush.
:param objects: Optional; restricts the flush operation to operate
only on elements that are in the given collection.
This feature is for an extremely narrow set of use cases where
particular objects may need to be operated upon before the
full flush() occurs. It is not intended for general use.
zSession is already flushingNTF)rv rG rH r _flush)rM objectss r" rw z
Session.flush st 6 > L,-JKK K >> F # !DN KK "DNNNUDN " " " "s A A!c 4 t j d|z d S )NzUsage of the '%s' operation is not currently supported within the execution stage of the flush process. Results may not be consistent. Consider using alternative event listeners or connection-level operations instead.)r r )rM methods r" r zSession._flush_warning s3
F IO
O
r* c V | j o| j o| j S rS )r check_modifiedrs rr rQ s r" r zSession._is_clean s5 !0022 2
M!
I
r* c N | j }|s.| j s'| j s | j j d S t
| }| j j r#| j | || | j }t | j }t | j }t |
| }|rt }|D ]q} t j | }nD# t j $ r2} t j t j | | Y d } ~ nd } ~ ww xY w| | rnd }t }
|r<| | |
| } n(| |
| } | D ]}t+ | | } | o|j }
| r |
s |j r| |g O| ||
}|s
J d |
| |r)| |
|
} n|
|
} | D ]%}| |d }|s
J d &|j sd S | d x|_ } d| _ | d| _ n # d| _ w xY w| j | | |! |sv| j j rjtE | j j }tF j$ % d | j j D | j t j& d |z | j ' | | |( d S # t j) 5 |* d
d d d Y d S # 1 swxY w Y Y d S xY w) Nr )isdeletez*Failed to add object to the flush context!Tr Fc g | ] }||j f S r: rn ro s r" rh z"Session._flush..^
s/ !
+ r* )r zAttribute history events accumulated on %d previously clean instances within inner-flush event handlers have been reset, and will not result in database updates. Consider using set_committed_value() within inner-flush event handlers to avoid this warning.r )+
_dirty_statesrs rr r r r r rK before_flushr~
differencer rH r rI r r rJ r r rt r
_is_orphan has_identityrw r register_objecthas_workr r r r after_flushfinalize_flush_changesr r r rx r after_flush_postexecr r r )rM r dirty
flush_contextdeletednewobjsetr\ r r' processedproc is_orphanis_persistent_orphan_regr len_s r" r zSession._flush s " T] 49 ' - - / / / F&t,,
= % ' M & &t]G D D D &Edm$$$)nnE
%%g.. UUF
"
" & 5a 8 8EE| K1!44(+
5!!!!
" F EE 899U##0088CCGLLDD99U##..w77D % %E%e,,77>>I#,#C1C
%,
% 6
%
$$eW----$44$8 5 II IIIt
e$$$$ 1''//::9EEDD%%i00D F FE 000FFD E EE E E4 E % F26** 3= 3
3
!K+ >#'D
- %%'''',$$u$,,,, M % %dM : : : 0 0 2 2 2
t 0 :
4,677&99 %)%6%@ #'"3 : H
KO O
M . .t] C C C >"$$
>
>$$$===
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>sa C**D+9(D&&D+O K8 0O 8 LCO P$1P P$P P$ P P$c
d }d |D }|st || }t j || D ]#\ \ }}} | || |d||d $dS )a Perform a bulk save of the given list of objects.
The bulk save feature allows mapped objects to be used as the
source of simple INSERT and UPDATE operations which can be more easily
grouped together into higher performing "executemany"
operations; the extraction of data from the objects is also performed
using a lower-latency process that ignores whether or not attributes
have actually been modified in the case of UPDATEs, and also ignores
SQL expressions.
The objects as given are not added to the session and no additional
state is established on them, unless the ``return_defaults`` flag
is also set, in which case primary key attributes and server-side
default values will be populated.
.. versionadded:: 1.0.0
.. warning::
The bulk save feature allows for a lower-latency INSERT/UPDATE
of rows at the expense of most other unit-of-work features.
Features such as object management, relationship handling,
and SQL clause support are **silently omitted** in favor of raw
INSERT/UPDATES of records.
**Please read the list of caveats at**
:ref:`bulk_operations_caveats` **before using this method, and
fully test and confirm the functionality of all code developed
using these systems.**
:param objects: a sequence of mapped object instances. The mapped
objects are persisted as is, and are **not** associated with the
:class:`.Session` afterwards.
For each object, whether the object is sent as an INSERT or an
UPDATE is dependent on the same rules used by the :class:`.Session`
in traditional operation; if the object has the
:attr:`.InstanceState.key`
attribute set, then the object is assumed to be "detached" and
will result in an UPDATE. Otherwise, an INSERT is used.
In the case of an UPDATE, statements are grouped based on which
attributes have changed, and are thus to be the subject of each
SET clause. If ``update_changed_only`` is False, then all
attributes present within each object are applied to the UPDATE
statement, which may help in allowing the statements to be grouped
together into a larger executemany(), and will also reduce the
overhead of checking history on attributes.
:param return_defaults: when True, rows that are missing values which
generate defaults, namely integer primary key defaults and sequences,
will be inserted **one at a time**, so that the primary key value
is available. In particular this will allow joined-inheritance
and other multi-table mappings to insert correctly without the need
to provide primary key values ahead of time; however,
:paramref:`.Session.bulk_save_objects.return_defaults` **greatly
reduces the performance gains** of the method overall.
:param update_changed_only: when True, UPDATE statements are rendered
based on those attributes in each state that have logged changes.
When False, all attributes present are rendered into the SET clause
with the exception of primary key attributes.
:param preserve_order: when True, the order of inserts and updates
matches exactly the order in which the objects are given. When
False, common types of objects are grouped into inserts
and updates, to allow for more batching opportunities.
.. versionadded:: 1.3
.. seealso::
:ref:`bulk_operations`
:meth:`.Session.bulk_insert_mappings`
:meth:`.Session.bulk_update_mappings`
c " | j | j d ufS rS )r r r
s r" r z&Session.bulk_save_objects..key
s L%)4"78 8r* c 3 > K | ]}t j | V d S rS )r rH )rg rr s r" rp z,Session.bulk_save_objects..
s- HHj/44HHHHHHr* )r TFN)sorted itertoolsgroupby_bulk_save_mappings)
rM r return_defaultsupdate_changed_onlypreserve_orderr
obj_statesr isupdaterk s
r" r zSession.bulk_save_objects|
s n 9 9 9 IHHHH
5
444J*3*;J*L*L & VX $ $ #
r* c < | ||dd|d| dS )aF Perform a bulk insert of the given list of mapping dictionaries.
The bulk insert feature allows plain Python dictionaries to be used as
the source of simple INSERT operations which can be more easily
grouped together into higher performing "executemany"
operations. Using dictionaries, there is no "history" or session
state management features in use, reducing latency when inserting
large numbers of simple rows.
The values within the dictionaries as given are typically passed
without modification into Core :meth:`_expression.Insert` constructs,
after
organizing the values within them across the tables to which
the given mapper is mapped.
.. versionadded:: 1.0.0
.. warning::
The bulk insert feature allows for a lower-latency INSERT
of rows at the expense of most other unit-of-work features.
Features such as object management, relationship handling,
and SQL clause support are **silently omitted** in favor of raw
INSERT of records.
**Please read the list of caveats at**
:ref:`bulk_operations_caveats` **before using this method, and
fully test and confirm the functionality of all code developed
using these systems.**
:param mapper: a mapped class, or the actual :class:`_orm.Mapper`
object,
representing the single kind of object represented within the mapping
list.
:param mappings: a sequence of dictionaries, each one containing the
state of the mapped row to be inserted, in terms of the attribute
names on the mapped class. If the mapping refers to multiple tables,
such as a joined-inheritance mapping, each dictionary must contain all
keys to be populated into all tables.
:param return_defaults: when True, rows that are missing values which
generate defaults, namely integer primary key defaults and sequences,
will be inserted **one at a time**, so that the primary key value
is available. In particular this will allow joined-inheritance
and other multi-table mappings to insert correctly without the need
to provide primary
key values ahead of time; however,
:paramref:`.Session.bulk_insert_mappings.return_defaults`
**greatly reduces the performance gains** of the method overall.
If the rows
to be inserted only refer to a single table, then there is no
reason this flag should be set as the returned default information
is not used.
:param render_nulls: When True, a value of ``None`` will result
in a NULL value being included in the INSERT statement, rather
than the column being omitted from the INSERT. This allows all
the rows being INSERTed to have the identical set of columns which
allows the full set of rows to be batched to the DBAPI. Normally,
each column-set that contains a different combination of NULL values
than the previous row must omit a different series of columns from
the rendered INSERT statement, which means it must be emitted as a
separate statement. By passing this flag, the full set of rows
are guaranteed to be batchable into one batch; the cost however is
that server-side defaults which are invoked by an omitted column will
be skipped, so care must be taken to ensure that these are not
necessary.
.. warning::
When this flag is set, **server side default SQL values will
not be invoked** for those columns that are inserted as NULL;
the NULL value will be sent explicitly. Care must be taken
to ensure that no server-side default functions need to be
invoked for the operation as a whole.
.. versionadded:: 1.1
.. seealso::
:ref:`bulk_operations`
:meth:`.Session.bulk_save_objects`
:meth:`.Session.bulk_update_mappings`
FNr )rM r mappingsr render_nullss r" r z Session.bulk_insert_mappings
s< v
r* c < | ||ddddd dS )a Perform a bulk update of the given list of mapping dictionaries.
The bulk update feature allows plain Python dictionaries to be used as
the source of simple UPDATE operations which can be more easily
grouped together into higher performing "executemany"
operations. Using dictionaries, there is no "history" or session
state management features in use, reducing latency when updating
large numbers of simple rows.
.. versionadded:: 1.0.0
.. warning::
The bulk update feature allows for a lower-latency UPDATE
of rows at the expense of most other unit-of-work features.
Features such as object management, relationship handling,
and SQL clause support are **silently omitted** in favor of raw
UPDATES of records.
**Please read the list of caveats at**
:ref:`bulk_operations_caveats` **before using this method, and
fully test and confirm the functionality of all code developed
using these systems.**
:param mapper: a mapped class, or the actual :class:`_orm.Mapper`
object,
representing the single kind of object represented within the mapping
list.
:param mappings: a sequence of dictionaries, each one containing the
state of the mapped row to be updated, in terms of the attribute names
on the mapped class. If the mapping refers to multiple tables, such
as a joined-inheritance mapping, each dictionary may contain keys
corresponding to all tables. All those keys which are present and
are not part of the primary key are applied to the SET clause of the
UPDATE statement; the primary key values, which are required, are
applied to the WHERE clause.
.. seealso::
:ref:`bulk_operations`
:meth:`.Session.bulk_insert_mappings`
:meth:`.Session.bulk_save_objects`
TFNr )rM r r s r" r z Session.bulk_update_mappingsJ s6 b
HdE5%
r* c t | }d| _ | d } |rt j ||||| nt j |||||| | nH# t j 5 | d d d d n # 1 swxY w Y Y nxY wd| _ d S # d| _ w xY w)NTr r F)
r rv r r _bulk_update _bulk_insertr r r r ) rM r r r isstatesr r r r s r" r zSession._bulk_save_mappings sG "&)) jjj66 #
( ' ( #
>"$$
>
>$$$===
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> #DNNNUDN " " " "sB AA7 6C 7B< B/# B</B3 3B<6B3 7B<:C C)z0.8zThe :paramref:`.Session.is_modified.passive` flag is deprecated and will be removed in a future release. The flag is no longer used and is ignored.r c t | }|j sdS |j }|j j D ]a}|st |j d st |j d s/|j ||t j \ }}} |s| r dS bdS )aZ
Return ``True`` if the given instance has locally
modified attributes.
This method retrieves the history for each instrumented
attribute on the instance and performs a comparison of the current
value to its previously committed value, if any.
It is in effect a more expensive and accurate
version of checking for the given instance in the
:attr:`.Session.dirty` collection; a full test for
each attribute's net "dirty" status is performed.
E.g.::
return session.is_modified(someobject)
A few caveats to this method apply:
* Instances present in the :attr:`.Session.dirty` collection may
report ``False`` when tested with this method. This is because
the object may have received change events via attribute mutation,
thus placing it in :attr:`.Session.dirty`, but ultimately the state
is the same as that loaded from the database, resulting in no net
change here.
* Scalar attributes may not have recorded the previously set
value when a new value was applied, if the attribute was not loaded,
or was expired, at the time the new value was received - in these
cases, the attribute is assumed to have a change, even if there is
ultimately no net change against its database value. SQLAlchemy in
most cases does not need the "old" value when a set event occurs, so
it skips the expense of a SQL call if the old value isn't present,
based on the assumption that an UPDATE of the scalar value is
usually needed, and in those few cases where it isn't, is less
expensive on average than issuing a defensive SELECT.
The "old" value is fetched unconditionally upon set only if the
attribute container has the ``active_history`` flag set to ``True``.
This flag is set typically for primary key attributes and scalar
object references that are not a simple many-to-one. To set this
flag for any arbitrary mapped column, use the ``active_history``
argument with :func:`.column_property`.
:param instance: mapped instance to be tested for pending changes.
:param include_collections: Indicates if multivalued collections
should be included in the operation. Setting this to ``False`` is a
way to detect only local-column based properties (i.e. scalar columns
or many-to-one foreign keys) that would result in an UPDATE for this
instance upon flush.
:param passive: not used
Fget_collection get_historyr T) r r r rX r hasattrimplr NO_CHANGE)
rM r2 include_collectionsr r dict_attradded unchangedr s
r" r zSession.is_modified s x X&&~ 5
M, D'
DI'788
TY
66
*.)*?*?uj&: +@ + + 'UIw
tt
5r* c ( | j o | j j S )a2 True if this :class:`.Session` is in "transaction mode" and
is not in "partial rollback" state.
The :class:`.Session` in its default mode of ``autocommit=False``
is essentially always in "transaction mode", in that a
:class:`.SessionTransaction` is associated with it as soon as
it is instantiated. This :class:`.SessionTransaction` is immediately
replaced with a new one as soon as it is ended, due to a rollback,
commit, or close operation.
"Transaction mode" does *not* indicate whether
or not actual database connection resources are in use; the
:class:`.SessionTransaction` object coordinates among zero or more
actual database transactions, and starts out with none, accumulating
individual DBAPI connections as different data sources are used
within its scope. The best way to track when a particular
:class:`.Session` has actually begun to use DBAPI resources is to
implement a listener using the :meth:`.SessionEvents.after_begin`
method, which will deliver both the :class:`.Session` as well as the
target :class:`_engine.Connection` to a user-defined event listener.
The "partial rollback" state refers to when an "inner" transaction,
typically used during a flush, encounters an error and emits a
rollback of the DBAPI connection. At this point, the
:class:`.Session` is in "partial rollback" and awaits for the user to
call :meth:`.Session.rollback`, in order to close out the
transaction stack. It is in this "partial rollback" period that the
:attr:`.is_active` flag returns False. After the call to
:meth:`.Session.rollback`, the :class:`.SessionTransaction` is
replaced with a new one and :attr:`.is_active` returns ``True`` again.
When a :class:`.Session` is used in ``autocommit=True`` mode, the
:class:`.SessionTransaction` is only instantiated within the scope
of a flush call, or when :meth:`.Session.begin` is called. So
:attr:`.is_active` will always be ``False`` outside of a flush or
:meth:`.Session.begin` block in this mode, and will be ``True``
within the :meth:`.Session.begin` block as long as it doesn't enter
"partial rollback" state.
From all the above, it follows that the only purpose to this flag is
for application frameworks that wish to detect if a "rollback" is
necessary within a generic error handling routine, for
:class:`.Session` objects that would otherwise be in
"partial rollback" mode. In a typical integration case, this is also
not necessary as it is standard practice to emit
:meth:`.Session.rollback` unconditionally within the outermost
exception catch.
To track the transactional state of a :class:`.Session` fully,
use event listeners, primarily the :meth:`.SessionEvents.after_begin`,
:meth:`.SessionEvents.after_commit`,
:meth:`.SessionEvents.after_rollback` and related events.
)r rT rQ s r" rT zSession.is_active s p >D$4$>>r* c 4 | j S )zThe set of all persistent states considered dirty.
This method returns all states that were modified including
those that were possibly deleted.
)r r rQ s r" r zSession._dirty_statesB s ..000r* c N t j fd j D S )aZ The set of all persistent instances considered dirty.
E.g.::
some_mapped_object in session.dirty
Instances are considered dirty when they were modified but not
deleted.
Note that this 'dirty' calculation is 'optimistic'; most
attribute-setting or collection modification operations will
mark an instance as 'dirty' and place it in this set, even if
there is no net change to the attribute's value. At flush
time, the value of each attribute is compared to its
previously saved value, and if there's no net change, no SQL
operation will occur (this is a more expensive operation so
it's only done at flush time).
To check if an instance has actionable net changes to its
attributes, use the :meth:`.Session.is_modified` method.
c J g | ] }|j v | S r: )rs rr )rg r rM s r" rh z!Session.dirty..e s8
-- ---r* )r IdentitySetr rQ s `r" r z
Session.dirtyL sC 0
! /
r* c r t j t | j S )zDThe set of all instances marked as 'deleted' within this ``Session``)r r r rs r rQ s r" r zSession.deletedl s+ T]%9%9%;%; < <===r* c r t j t | j S )zAThe set of all instances marked as 'new' within this ``Session``.)r r r rr r rQ s r" r z Session.newr s+ TY%5%5%7%7 8 8999r* ) NTTTFFNNNTNN)FF)NNNFNrS )NNN)NNr )T)TNN)FTTr )Nr3 r4 r5 r6 public_methodsr deprecated_paramsrO connection_callabler memoized_propertyr r r r r r rh rd r r r r r r r r* r- rc r r contextmanagerr> rC r r r rK rZ r8 rd r r r} ry r r r r r r r r rV r r r r r r r r r rw r r r r r r r r rT r r r r r r: r* r" r r k s N: T
(
! 4 '+ !
I( I( I(1 0I(V KF > > > > @' ' '2( ( (("" "" ""H# # #*
O
O
O
O
b J
J
J
J
X
+
+
+ * * *D. . .
@
@
@ 2% % %8$ $ $8A
A
A
A
F9 9 9 ' ' X'4A A A& ] ] ] ]~!C !C !CF,3 ,3 ,3 ,3\ . . . T_
' ) )
)N N N0
P! P! P!d: : :3 3 3(* * * *., , ,+ + +6 6 6& 1 1 1DM' M' M' M'f "
S S S Sj
+
+
+ $= $= $= $=L% % % ;+ ;+ ;+z
< < <+ + +
M M M$# $# $# $#L
{> {> {> {>@ g g g gT EJc
c
c
c
J3
3
3
j&# &# &#P T
I I I IV 7? 7? X7?r L 1 1 X1
X
> > > X>
: : X: : :r* r c 8 e Zd ZdZdeddddfdZd Zd Zd ZdS ) r a3 A configurable :class:`.Session` factory.
The :class:`.sessionmaker` factory generates new
:class:`.Session` objects when called, creating them given
the configurational arguments established here.
e.g.::
# global scope
Session = sessionmaker(autoflush=False)
# later, in a local scope, create and use a session:
sess = Session()
Any keyword arguments sent to the constructor itself will override the
"configured" keywords::
Session = sessionmaker()
# bind an individual session to a connection
sess = Session(bind=connection)
The class also includes a method :meth:`.configure`, which can
be used to specify additional keyword arguments to the factory, which
will take effect for subsequent :class:`.Session` objects generated.
This is usually used to associate one or more :class:`_engine.Engine`
objects
with an existing :class:`.sessionmaker` factory before it is first
used::
# application starts
Session = sessionmaker()
# ... later
engine = create_engine('sqlite:///foo.db')
Session.configure(bind=engine)
sess = Session()
.. seealso::
:ref:`session_getting` - introductory text on creating
sessions using :class:`.sessionmaker`.
NTFc ||d< ||d< ||d< ||d< |||d< || _ t |j |fi | _ dS )al Construct a new :class:`.sessionmaker`.
All arguments here except for ``class_`` correspond to arguments
accepted by :class:`.Session` directly. See the
:meth:`.Session.__init__` docstring for more details on parameters.
:param bind: a :class:`_engine.Engine` or other :class:`.Connectable`
with
which newly created :class:`.Session` objects will be associated.
:param class\_: class to use in order to create new :class:`.Session`
objects. Defaults to :class:`.Session`.
:param autoflush: The autoflush setting to use with newly created
:class:`.Session` objects.
:param autocommit: The autocommit setting to use with newly created
:class:`.Session` objects.
:param expire_on_commit=True: the
:paramref:`_orm.Session.expire_on_commit` setting to use
with newly created :class:`.Session` objects.
:param info: optional dictionary of information that will be available
via :attr:`.Session.info`. Note this dictionary is *updated*, not
replaced, when the ``info`` parameter is specified to the specific
:class:`.Session` construction operation.
.. versionadded:: 0.9.0
:param \**kw: all other keyword arguments are passed to the
constructor of newly created :class:`.Session` objects.
rg r r r Nr )r r$ r3 r )rM rg r r r r r r s r" rO zsessionmaker.__init__ s_ P 6
#;%<!1 BvJ 6?VIr:: r* c | j D ]Z\ }}|dk r9d|v r5| }| |d ||d< D| || [ | j di |S )ae Produce a new :class:`.Session` object using the configuration
established in this :class:`.sessionmaker`.
In Python, the ``__call__`` method is invoked on an object when
it is "called" in the same way as a function::
Session = sessionmaker()
session = Session() # invokes sessionmaker.__call__()
r r: )r r copyr
setdefaultr )rM local_kwkvds r" __call__zsessionmaker.__call__ s GMMOO * *DAqF{{v 1 1FFHH&)***#$ ##Aq))))t{&&X&&&r* c : | j | dS )z(Re)configure the arguments for this sessionmaker.
e.g.::
Session = sessionmaker()
Session.configure(bind=create_engine('sqlite://'))
N)r r )rM new_kws r" configurezsessionmaker.configure s
v r* c | j j d| j j dd d | j D dS )Nz(class_=r0 c 3 * K | ]\ }}|d |V dS )=Nr: )rg r! r" s r" rp z(sessionmaker.__repr__.. s1 CC41aAA&CCCCCCr* )) __class__r3 r r9 r r rQ s r" __repr__zsessionmaker.__repr__ sV N # # # K IICC47==??CCC C C C C
r* ) r3 r4 r5 r6 r rO r$ r' r- r: r* r" r r y su , ,`
1; 1; 1; 1;f' ' '(
r* r c f t D ]} | dS )aO Close all sessions in memory.
This function consults a global registry of all :class:`.Session` objects
and calls :meth:`.Session.close` on them, which resets them to a clean
state.
This function is not for general use but may be useful for test suites
within the teardown scheme.
.. versionadded:: 1.3
N)r r r )r s r" r' r'
s8 ""
r* c t j | }t | }|r| |g |j |j r|`|j r|`|j r|`dS dS )aM Alter the state of the given instance so that it is :term:`transient`.
.. note::
:func:`.make_transient` is a special-case function for
advanced use cases only.
The given mapped instance is assumed to be in the :term:`persistent` or
:term:`detached` state. The function will remove its association with any
:class:`.Session` as well as its :attr:`.InstanceState.identity`. The
effect is that the object will behave as though it were newly constructed,
except retaining any attribute / collection values that were loaded at the
time of the call. The :attr:`.InstanceState.deleted` flag is also reset
if this object had been deleted as a result of using
:meth:`.Session.delete`.
.. warning::
:func:`.make_transient` does **not** "unexpire" or otherwise eagerly
load ORM-mapped attributes that are not currently loaded at the time
the function is called. This includes attributes which:
* were expired via :meth:`.Session.expire`
* were expired as the natural effect of committing a session
transaction, e.g. :meth:`.Session.commit`
* are normally :term:`lazy loaded` but are not currently loaded
* are "deferred" via :ref:`deferred` and are not yet loaded
* were not present in the query which loaded this object, such as that
which is common in joined table inheritance and other scenarios.
After :func:`.make_transient` is called, unloaded attributes such
as those above will normally resolve to the value ``None`` when
accessed, or an empty collection for a collection-oriented attribute.
As the object is transient and un-associated with any database
identity, it will no longer retrieve these values.
.. seealso::
:func:`.make_transient_to_detached`
N) r rH r# r expired_attributesr callablesr rs )r2 r r s r" make_transientr2
s \
%h / /Eu A # 5'"""
""$$$
O y I ~ NNN r* c 6 t j | }|j s|j rt j d |j | |_ |j r|`| |j
| |j
|j dS )a Make the given transient instance :term:`detached`.
.. note::
:func:`.make_transient_to_detached` is a special-case function for
advanced use cases only.
All attribute history on the given instance
will be reset as though the instance were freshly loaded
from a query. Missing attributes will be marked as expired.
The primary key attributes of the object, which are required, will be made
into the "key" of the instance.
The object can then be added to a session, or merged
possibly with the load=False flag, at which point it will look
as if it were loaded that way, without emitting SQL.
This is a special use case function that differs from a normal
call to :meth:`.Session.merge` in that a given persistent state
can be manufactured without any SQL calls.
.. versionadded:: 0.9.5
.. seealso::
:func:`.make_transient`
:meth:`.Session.enable_relationship_loading`
z Given object must be transientN)
r rH r r rG rH r rs rs r r rW unloaded_expirable)r2 r s r" make_transient_to_detachedr5 T
s >
%h / /E K59 K()IJJJ 55e< r? r r r r' r2 r5 r1 counterr r: r* r" rA sm 8 7
" " " " " " 3 3 3 3 3 3 & & & & & & " " " " " " P
O
O 'G ' ) ) ?
!( !( !( !( !(6 !( !( !(H
X 4;z " " DK $ $ 4;z " " X C C C C C C C C LK(: K(: K(: K(: K(:" K(: K(: K(:\PF
F
F
F
F
' F
F
F
R $= = =@&C &C &CR% % %& r*