Why Gemfury?
Push, build, and install
RubyGems
npm packages
Python packages
Maven artifacts
PHP packages
Go Modules
Debian packages
RPM packages
NuGet packages
triliodata-4-0-patch / contego deb
Repository URL to install this package:
|
Version:
4.0.108 ▾
|
contego
/
home
/
tvault
/
.virtenv
/
lib
/
python2.7
/
site-packages
/
sqlalchemy
/
orm
/
session.pyc
|
|---|
ó
EYc @ sÿ d Z d d l Z d d l m Z m Z m Z m Z d d l m Z m Z d d l m
Z
m Z m Z m Z m
Z
m Z d d l m Z d d l m Z m Z m Z m Z m Z m Z m Z m Z d d l Z d d
l m Z d d l m Z d d l m Z d d l Z d
d d d g Z! e j" Z# d Z$ d e% f d YZ& e j' d Z( e j' d Z) e j' d Z* e j' d Z+ e j' d Z, d e% f d YZ- d
e& f d YZ. d e& f d YZ/ d Z0 d Z1 d Z2 e j3 Z4 d S( s1 Provides the Session class and related utilities.iÿÿÿÿNi ( t utilt sqlt enginet exc( R t
expressioni ( t SessionExtensiont
attributesR t queryt loadingt identity( t inspect( t
object_mappert class_mappert _class_to_mappert
_state_mappert object_statet _none_sett state_strt instance_str( t persistence( t UOWTransaction( t statet Sessiont SessionTransactionR t sessionmakerc C s3 | j r/ y t | j SWq/ t k
r+ q/ Xn d S( s_ Given an :class:`.InstanceState`, return the :class:`.Session`
associated, if any.
N( t
session_idt _sessionst KeyErrort None( R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _state_session% s
t _SessionClassMethodsc B sJ e Z d Z e d Z e e j d d Z e d Z RS( sB Class-level methods for :class:`.Session`, :class:`.sessionmaker`.c C s% x t j D] } | j q
Wd S( s Close *all* sessions in memory.N( R t valuest close( t clst sess( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt close_all4 s s sqlalchemy.orm.utilc O s | j | | S( sZ Return an identity key.
This is an alias of :func:`.util.identity_key`.
( t identity_key( R! t orm_utilt argst kwargs( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR$ ; s c C s
t | S( sx Return the :class:`.Session` to which an object belongs.
This is an alias of :func:`.object_session`.
( t object_session( R! t instance( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR( E s ( t __name__t
__module__t __doc__t classmethodR# R t dependenciesR$ R( ( ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR 1 s
t ACTIVEt PREPAREDt COMMITTEDt DEACTIVEt CLOSEDc B s e Z d Z d Z d e d Z e d Z e Z e d Z
e e e d d Z e d Z d d Z
e d Z d d Z d
Z e d Z d Z d
Z d Z d Z d Z e d Z d Z e d Z d Z d Z RS( s A :class:`.Session`-level transaction.
:class:`.SessionTransaction` is a mostly behind-the-scenes object
not normally referenced directly by application code. It coordinates
among multiple :class:`.Connection` objects, maintaining a database
transaction for each one individually, committing or rolling them
back all at once. It also provides optional two-phase commit behavior
which can augment this coordination operation.
The :attr:`.Session.transaction` attribute of :class:`.Session`
refers to the current :class:`.SessionTransaction` object in use, if any.
The :attr:`.SessionTransaction.parent` attribute refers to the parent
:class:`.SessionTransaction` in the stack of :class:`.SessionTransaction`
objects. If this attribute is ``None``, then this is the top of the stack.
If non-``None``, then this :class:`.SessionTransaction` refers either
to a so-called "subtransaction" or a "nested" transaction. A
"subtransaction" is a scoping concept that demarcates an inner portion
of the outermost "real" transaction. A nested transaction, which
is indicated when the :attr:`.SessionTransaction.nested`
attribute is also True, indicates that this :class:`.SessionTransaction`
corresponds to a SAVEPOINT.
**Life Cycle**
A :class:`.SessionTransaction` is associated with a :class:`.Session`
in its default mode of ``autocommit=False`` immediately, associated
with no database connections. As the :class:`.Session` is called upon
to emit SQL on behalf of various :class:`.Engine` or :class:`.Connection`
objects, a corresponding :class:`.Connection` and associated
:class:`.Transaction` is added to a collection within the
:class:`.SessionTransaction` object, becoming one of the
connection/transaction pairs maintained by the
:class:`.SessionTransaction`. The start of a :class:`.SessionTransaction`
can be tracked using the :meth:`.SessionEvents.after_transaction_create`
event.
The lifespan of the :class:`.SessionTransaction` ends when the
:meth:`.Session.commit`, :meth:`.Session.rollback` or
:meth:`.Session.close` methods are called. At this point, the
:class:`.SessionTransaction` removes its association with its parent
:class:`.Session`. A :class:`.Session` that is in ``autocommit=False``
mode will create a new :class:`.SessionTransaction` to replace it
immediately, whereas a :class:`.Session` that's in ``autocommit=True``
mode will remain without a :class:`.SessionTransaction` until the
:meth:`.Session.begin` method is called. The end of a
:class:`.SessionTransaction` can be tracked using the
:meth:`.SessionEvents.after_transaction_end` event.
**Nesting and Subtransactions**
Another detail of :class:`.SessionTransaction` behavior is that it is
capable of "nesting". This means that the :meth:`.Session.begin` method
can be called while an existing :class:`.SessionTransaction` is already
present, producing a new :class:`.SessionTransaction` that temporarily
replaces the parent :class:`.SessionTransaction`. When a
:class:`.SessionTransaction` is produced as nested, it assigns itself to
the :attr:`.Session.transaction` attribute, and it additionally will assign
the previous :class:`.SessionTransaction` to its :attr:`.Session.parent`
attribute. The behavior is effectively a
stack, where :attr:`.Session.transaction` refers to the current head of
the stack, and the :attr:`.SessionTransaction.parent` attribute allows
traversal up the stack until :attr:`.SessionTransaction.parent` is
``None``, indicating the top of the stack.
When the scope of :class:`.SessionTransaction` is ended via
:meth:`.Session.commit` or :meth:`.Session.rollback`, it restores its
parent :class:`.SessionTransaction` back onto the
:attr:`.Session.transaction` attribute.
The purpose of this stack is to allow nesting of
:meth:`.Session.rollback` or :meth:`.Session.commit` calls in context
with various flavors of :meth:`.Session.begin`. This nesting behavior
applies to when :meth:`.Session.begin_nested` is used to emit a
SAVEPOINT transaction, and is also used to produce a so-called
"subtransaction" which allows a block of code to use a
begin/rollback/commit sequence regardless of whether or not its enclosing
code block has begun a transaction. The :meth:`.flush` method, whether
called explicitly or via autoflush, is the primary consumer of the
"subtransaction" feature, in that it wishes to guarantee that it works
within in a transaction block regardless of whether or not the
:class:`.Session` is in transactional mode when the method is called.
Note that the flush process that occurs within the "autoflush" feature
as well as when the :meth:`.Session.flush` method is used **always**
creates a :class:`.SessionTransaction` object. This object is normally
a subtransaction, unless the :class:`.Session` is in autocommit mode
and no transaction exists at all, in which case it's the outermost
transaction. Any event-handling logic or other inspection logic
needs to take into account whether a :class:`.SessionTransaction`
is the outermost transaction, a subtransaction, or a "nested" / SAVEPOINT
transaction.
.. seealso::
:meth:`.Session.rollback`
:meth:`.Session.commit`
:meth:`.Session.begin`
:meth:`.Session.begin_nested`
:attr:`.Session.is_active`
:meth:`.SessionEvents.after_transaction_create`
:meth:`.SessionEvents.after_transaction_end`
:meth:`.SessionEvents.after_commit`
:meth:`.SessionEvents.after_rollback`
:meth:`.SessionEvents.after_soft_rollback`
c C s | | _ i | _ | | _ | | _ t | _ | rL | rL t j d n | j j re | j n | j j
j r | j j
j | j | n d S( NsO Can't start a SAVEPOINT transaction when no existing transaction is in progress( t sessiont _connectionst _parentt nestedR/ t _statet sa_exct InvalidRequestErrort _enable_transaction_accountingt _take_snapshott dispatcht after_transaction_create( t selfR4 t parentR7 ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt __init__Î s
c C s | j S( sj The parent :class:`.SessionTransaction` of this
:class:`.SessionTransaction`.
If this attribute is ``None``, indicates this
:class:`.SessionTransaction` is at the top of the stack, and
corresponds to a real "COMMIT"/"ROLLBACK"
block. If non-``None``, then this is either a "subtransaction"
or a "nested" / SAVEPOINT transaction. If the
:attr:`.SessionTransaction.nested` attribute is ``True``, then
this is a SAVEPOINT, and if ``False``, indicates this a subtransaction.
.. versionadded:: 1.0.16 - use ._parent for previous versions
( R6 ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR@ ß s c C s | j d k o | j t k S( N( R4 R R8 R/ ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt is_activeù s s This transaction is closedc C sÍ | j t k r! t j d n¨ | j t k rK | sÉ t j d qÉ n~ | j t k r¨ | rÉ | rÉ | j r t j d | j q¥ | s¥ t j d q¥ qÉ n! | j t k rÉ t j | n d S( Ns\ This session is in 'committed' state; no further SQL can be emitted within this transaction.s[ This session is in 'prepared' state; no further SQL can be emitted within this transaction.s This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: %ss This Session's transaction has been rolled back by a nested rollback() call. To begin a new transaction, issue Session.rollback() first.( R8 R1 R9 R: R0 R2 t _rollback_exceptionR3 t ResourceClosedError( R? t prepared_okt rollback_okt deactive_okt
closed_msg( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _assert_activeý s$ c C s | j p | j S( N( R7 R6 ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _is_transaction_boundary s c K s/ | j | j j | | } | j | | S( N( RI R4 t get_bindt _connection_for_bind( R? t bindkeyt execution_optionsR' t bind( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt
connection$ s
c C s | j t | j | d | S( NR7 ( RI R R4 ( R? R7 ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _begin) s
c C sk | } d } xX | rf | | f 7} | j | k r5 Pq | j d k rZ t j d | q | j } q W| S( Ns4 Transaction %s is not on the active transaction list( ( R6 R R9 R: ( R? t uptot currentt result( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _iterate_parents. s
c C s¥ | j sI | j j | _ | j j | _ | j j | _ | j j | _ d S| j j se | j j n t j
| _ t j
| _ t j
| _ t j
| _ d S( N( RJ R6 t _newt _deletedt _dirtyt
_key_switchesR4 t _flushingt flusht weakreft WeakKeyDictionary( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR< ? s c C sr | j s t xH t | j j | j j D]( } | j j | | j r. | ` q. q. WxR | j j D]A \ } \ } } | j j
j | | | _ | j j
j | qj WxN t | j
j | j j
D]. } | j ræ | ` n | j j | d t qÎ W| j j
st xX | j j
j D]D } | sK| j sK| | j k r&| j | j | j j
j q&q&Wd S( Nt discard_existing( RJ t AssertionErrort setRV t unionR4 t _expunge_statet keyRY t itemst identity_mapt safe_discardt replaceRW t deletedt _update_implt Truet
all_statest modifiedRX t _expiret dictt _modified( R? t
dirty_onlyt st oldkeyt newkey( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _restore_snapshotO s" %
" % c C sú | j s t | j r | j j r x6 | j j j D]" } | j | j | j j j q8 Wx! t
| j D] } | j qn W| j j
nd | j rö | j j j | j | j j j | j | j j j | j | j j j | j n d S( N( RJ R_ R7 R4 t expire_on_commitRe Rk Rm Rn Ro t listRW t _detacht clearR6 RV t updateRX RY ( R? Rq ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _remove_snapshoth s c C sg | j | | j k r> | r/ t j d n | j | d S| j rl | j j | | } | j s· | SnK t | t j r« | } | j | j k r· t
j d q· n | j } | rÏ | j
| } n | j j rù | j d k rù | j } n$ | j r| j } n | j } | | | | k f | j | <| j | j <| j j j | j | | | S( NsO Connection is already established for the given bind; execution_options ignoredi sM Session already has a Connection associated for the given Connection's Engine( RI R5 R t warnR6 RL R7 t
isinstanceR t
ConnectionR9 R: t contextual_connectRN R4 t twophaseR t begin_twophaset begin_nestedt beginR= t after_begin( R? RO RN t connt transaction( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRL w s4
* c C s< | j d k s | j j r. t j d n | j d S( NsD 'twophase' mode not enabled, or not root transaction; can't prepare.( R6 R R4 R R9 R: t
_prepare_impl( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt prepare s c C sV | j | j d k s" | j r; | j j j | j n | j j } | | k r} x' | j d | D] } | j qf Wn | j j
sÒ xF t d D]& } | j j r¯ Pn | j j
q Wt j d n | j d k rI| j j rIy2 x+ t | j j D] } | d j qWWqIt j | j Wd QXqIXn t | _ d S( NRR id sr Over 100 subsequent flushes have occurred within session.commit() - is an after_flush() hook creating new objects?i ( RI R6 R R7 R4 R= t
before_commitR
RU t commitRZ t ranget _is_cleanR[ R t
FlushErrorR R` R5 R R R t safe_reraiset rollbackR0 R8 ( R? t stxt subtransactiont _flush_guardt t( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR ¥ s,
c C s¾ | j d t | j t k r, | j n | j d k sD | j r x+ t | j j
D] } | d j qZ Wt | _ | j
j j | j
| j
j r | j q n | j | j S( NRE i ( RI Rj R8 R0 R R6 R R7 R` R5 R R R1 R4 R= t after_commitR; Rz R ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR Ä s
c C sY | j d t d t | j j } | | k rX x' | j d | D] } | j qA Wn | } | j t t f k rË xU | j D]D } | j d k s | j r» | j t
| _ | } Pq t
| _ q Wn | j } | j r
| j r
t j d | j d | j n | j | j r?| r?t j d | j _ n | j j | | | j S( NRE RF RR s\ Session's state has been changed on a non-active transaction - this state will be discarded.Rp i ( RI Rj R4 R
RU R R8 R/ R0 R6 R R7 t _rollback_implR2 R; R R R{ Rt t syst exc_infoRC R= t after_soft_rollback( R? t _capture_exceptionR R t boundaryR
R" ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR Ö s2
c C sj x+ t | j j D] } | d j q W| j j rP | j d | j n | j j j | j d S( Ni Rp (
R` R5 R R R4 R; Rt R7 R= t after_rollback( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR þ s
c C sò | j | j _ | j d k rz xY t | j j D]? \ } } } | rV | j n | ri | j q4 | j q4 Wn t | _
| j j j r® | j j j | j | n | j d k rÜ | j j
sÜ | j j qÜ n d | _ d | _ d S( N( R6 R4 R
R R` R5 R t
invalidateR R3 R8 R= t after_transaction_endt
autocommitR ( R? R RP R
t autoclose( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR s" "
c C s | S( N( ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt __enter__ s c C s~ | j d t d t | j j d k r, d S| d k rp y | j Wqz t j | j Wd QXqz Xn
| j d S( NRG RE ( RI Rj R4 R
R R R R R ( R? t typet valuet traceback( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt __exit__ s
N( R* R+ R, R RC t FalseRA t propertyR@ R7 RB RI RJ RP RQ RU R< Rt Rz RL R R R R R R R R£ ( ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR W s4 s ' ( c B s5 e Z d Z d] Z d^ e e e e e e d^ d^ d^ e j d Z d^ Z
d^ Z e j
d Z e e d Z d Z d Z d Z d! Z d^ d^ d^ e d^ d" Z d^ d# Z d^ d^ d^ d$ Z d^ d^ d^ d% Z d& Z d' Z d( Z d) Z d* Z d+ Z d, Z d^ d^ d- Z d. Z e e j! d/ Z" d0 Z# d^ d^ d1 Z$ d2 Z% d^ d3 Z& d4 Z' d5 Z( e j) d6 d7 d8 Z* d9 Z+ d: Z, d; Z- d< Z. d= Z/ e d> Z0 d? Z1 d@ Z2 dA Z3 e dB Z4 e d^ dC Z5 dD Z6 dE Z7 e dF Z8 dG Z9 dH Z: dI Z; e dJ Z< e dK Z= dL Z> dM Z? dN Z@ d^ dO ZA dP ZB dQ ZC d^ dR ZD e e dS ZE e dT ZF dU ZG dV ZH e e dW ZI e dX ZJ d^ ZK e dY ZL e dZ ZM e d[ ZN e d\ ZO RS(_ s Manages persistence operations for ORM-mapped objects.
The Session's usage paradigm is described at :doc:`/orm/session`.
t __contains__t __iter__t addt add_allR R R R RP t deletet executet expiret
expire_allt expunget expunge_allR[ RK t is_modifiedt bulk_save_objectst bulk_insert_mappingst bulk_update_mappingst mergeR t refreshR t scalarc C sm | r t j | _ n t j d t j | _ | j | _ i | _ i | _ | | _ i | _
t | _ t | _
d | _ t | _ | | _ | | _ | | _ | | _ | | _ | | _ |
r× | j j |
n | r
x* t j | D] } t j | | qí Wn | d k rFx- | j D] \ }
} | j |
| q#Wn | j s\| j n | t | j <d S( s 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` or :class:`.Connection` to
which this ``Session`` should be bound. When specified, all SQL
operations performed by this session will execute via this
connectable.
:param binds: An optional dictionary which contains more granular
"bind" information than the ``bind`` parameter provides. This
dictionary can map individual :class`.Table`
instances as well as :class:`~.Mapper` instances to individual
:class:`.Engine` or :class:`.Connection` objects. Operations which
proceed relative to a particular :class:`.Mapper` will consult this
dictionary for the direct :class:`.Mapper` instance as
well as the mapper's ``mapped_table`` attribute in order to locate
a connectable to use. The full resolution is described in the
:meth:`.Session.get_bind`.
Usage looks like::
Session = sessionmaker(binds={
SomeMappedClass: create_engine('postgresql://engine1'),
somemapper: create_engine('postgresql://engine2'),
some_table: create_engine('postgresql://engine3'),
})
Also see the :meth:`.Session.bind_mapper`
and :meth:`.Session.bind_table` methods.
: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_transaction_accounting: Defaults to ``True``. A
legacy-only flag which when ``False`` disables *all* 0.5-style
object accounting on transaction boundaries, including auto-expiry
of instances on rollback and commit, maintenance of the "new" and
"deleted" lists upon rollback, and autoflush of pending changes
upon :meth:`~.Session.begin`, all of which are interdependent.
: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.
: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. **Deprecated.**
Please see :class:`.SessionEvents`.
: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`.
: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. **Deprecated** - this option
is present to allow compatibility with older applications, but
it is recommended that strong references to objects
be maintained by the calling application
externally to the :class:`.Session` itself,
to the extent that is required by the application.
s% weak_identity_map=False is deprecated. It is present to allow compatibility with older applications, but it is recommended that strong references to objects be maintained by the calling application externally to the :class:`.Session` itself, to the extent that is required by the application.N(! R t WeakInstanceDictt
_identity_clsR t warn_deprecatedt StrongInstanceDictRe RV RW RO t _Session__bindsR¤ RZ t _warn_on_eventsR R
t _new_sessionidt hash_keyt autoflushR Ru R; R t
_query_clst infoRy t to_listR t _adapt_listenerRd t _add_bindR R ( R? RO R¿ Ru R; R R t weak_identity_mapt bindst extensionRÁ t query_clst extRc ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRA ? s>
c C s i S( s« A user-modifiable dictionary.
The initial value of this dictionary can be populated using the
``info`` argument to the :class:`.Session` constructor or
:class:`.sessionmaker` constructor or factory methods. The dictionary
here is always local to this :class:`.Session` and can be modified
independently of all other :class:`.Session` objects.
.. versionadded:: 0.9.0
( ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRÁ ñ s
c C sd | j d k rH | s | r6 | j j d | | _ q] t j d n t | d | | _ | j S( sì Begin a transaction on this :class:`.Session`.
If this Session is already within a transaction, either a plain
transaction or nested transaction, an error is raised, unless
``subtransactions=True`` or ``nested=True`` is specified.
The ``subtransactions=True`` flag indicates that this
:meth:`~.Session.begin` can create a subtransaction if a transaction
is already in progress. For documentation on subtransactions, please
see :ref:`session_subtransactions`.
The ``nested`` flag begins a SAVEPOINT transaction and is equivalent
to calling :meth:`~.Session.begin_nested`. For documentation on
SAVEPOINT transactions, please see :ref:`session_begin_nested`.
R7 sS A transaction is already begun. Use subtransactions=True to allow subtransactions.N( R
R RQ R9 R: R ( R? t subtransactionsR7 ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR s c C s | j d t S( s Begin a `nested` transaction on this Session.
The target database(s) must support SQL SAVEPOINTs or a
SQLAlchemy-supported vendor implementation of the idea.
For documentation on SAVEPOINT
transactions, please see :ref:`session_begin_nested`.
R7 ( R Rj ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR s
c C s# | j d k r n
| j j d S( sØ Rollback the current transaction in progress.
If no transaction is in progress, this method is a pass-through.
This method rolls back the current transaction or nested transaction
regardless of subtransactions being in effect. All subtransactions up
to the first real transaction are closed. Subtransactions occur when
:meth:`.begin` is called multiple times.
.. seealso::
:ref:`session_rollback`
N( R
R R ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR * s c C sH | j d k r7 | j s% | j q7 t j d n | j j d S( s Flush pending changes and commit the current transaction.
If no transaction is in progress, this method raises an
:exc:`~sqlalchemy.exc.InvalidRequestError`.
By default, the :class:`.Session` also expires all database
loaded state on all ORM-managed attributes after transaction commit.
This so that subsequent operations load the most recent
data from the database. This behavior can be disabled using
the ``expire_on_commit=False`` option to :class:`.sessionmaker` or
the :class:`.Session` constructor.
If a subtransaction is in effect (which occurs when begin() is called
multiple times), the subtransaction will be closed, and the next call
to ``commit()`` will operate on the enclosing transaction.
When using the :class:`.Session` in its default mode of
``autocommit=False``, a new transaction will
be begun immediately after the commit, but note that the newly begun
transaction does *not* use any connection resources until the first
SQL is actually emitted.
.. seealso::
:ref:`session_committing`
s No transaction is begun.N( R
R R R R9 R: R ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR > s
c C sH | j d k r7 | j s% | j q7 t j d n | j j d S( sx Prepare the current transaction in progress for two phase commit.
If no transaction is in progress, this method raises an
:exc:`~sqlalchemy.exc.InvalidRequestError`.
Only root transactions of two phase sessions can be prepared. If the
current transaction is not such, an
:exc:`~sqlalchemy.exc.InvalidRequestError` is raised.
s No transaction is begun.N( R
R R R R9 R: R ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR b s
c K s@ | d k r' | j | d | | } n | j | d | d | S( s
Return a :class:`.Connection` object corresponding to this
:class:`.Session` object's transactional state.
If this :class:`.Session` is configured with ``autocommit=False``,
either the :class:`.Connection` corresponding to the current
transaction is returned, or if no transaction is in progress, a new
one is begun and the :class:`.Connection` returned (note that no
transactional state is established with the DBAPI until the first
SQL statement is emitted).
Alternatively, if this :class:`.Session` is configured with
``autocommit=True``, an ad-hoc :class:`.Connection` is returned
using :meth:`.Engine.contextual_connect` on the underlying
:class:`.Engine`.
Ambiguity in multi-bind or unbound :class:`.Session` objects can be
resolved through any of the optional keyword arguments. This
ultimately makes usage of the :meth:`.get_bind` method for resolution.
:param bind:
Optional :class:`.Engine` to be used as the bind. If
this engine is already involved in an ongoing transaction,
that connection will be used. This argument takes precedence
over ``mapper``, ``clause``.
:param mapper:
Optional :func:`.mapper` mapped class, used to identify
the appropriate bind. This argument takes precedence over
``clause``.
:param clause:
A :class:`.ClauseElement` (i.e. :func:`~.sql.expression.select`,
:func:`~.sql.expression.text`,
etc.) which will be used to locate a bind, if a bind
cannot otherwise be identified.
:param close_with_result: Passed to :meth:`.Engine.connect`,
indicating the :class:`.Connection` should be considered
"single use", automatically closing when the first result set is
closed. This flag only has an effect if this :class:`.Session` is
configured with ``autocommit=True`` and does not already have a
transaction in progress.
:param execution_options: a dictionary of execution options that will
be passed to :meth:`.Connection.execution_options`, **when the
connection is first procured only**. If the connection is already
present within the :class:`.Session`, a warning is emitted and
the arguments are ignored.
.. versionadded:: 0.9.9
.. seealso::
:ref:`session_transaction_isolation`
:param \**kw:
Additional keyword arguments are sent to :meth:`get_bind()`,
allowing additional arguments to be passed to custom
implementations of :meth:`get_bind`.
t clauset close_with_resultRN N( R RK RL ( R? t mapperRË RO RÌ RN t kw( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRP u s
B c K sQ | j d k r" | j j | | S| j | } | rI | j | } n | Sd S( N( R
R RL R~ RN ( R? R RN RÎ R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRL ¾ s
c K s[ t j | } | d k r6 | j | d | | } n | j | d t j | | pW i S( s Execute a SQL expression construct or string statement within
the current transaction.
Returns a :class:`.ResultProxy` representing
results of the statement execution, in the same manner as that of an
:class:`.Engine` or
:class:`.Connection`.
E.g.::
result = session.execute(
user_table.select().where(user_table.c.id == 5)
)
:meth:`~.Session.execute` accepts any executable clause construct,
such as :func:`~.sql.expression.select`,
:func:`~.sql.expression.insert`,
:func:`~.sql.expression.update`,
:func:`~.sql.expression.delete`, and
:func:`~.sql.expression.text`. Plain SQL strings can be passed
as well, which in the case of :meth:`.Session.execute` only
will be interpreted the same as if it were passed via a
:func:`~.expression.text` construct. That is, the following usage::
result = session.execute(
"SELECT * FROM user WHERE id=:param",
{"param":5}
)
is equivalent to::
from sqlalchemy import text
result = session.execute(
text("SELECT * FROM user WHERE id=:param"),
{"param":5}
)
The second positional argument to :meth:`.Session.execute` is an
optional parameter set. Similar to that of
:meth:`.Connection.execute`, whether this is passed as a single
dictionary, or a list of dictionaries, determines whether the DBAPI
cursor's ``execute()`` or ``executemany()`` is used to execute the
statement. An INSERT construct may be invoked for a single row::
result = session.execute(
users.insert(), {"id": 7, "name": "somename"})
or for multiple rows::
result = session.execute(users.insert(), [
{"id": 7, "name": "somename7"},
{"id": 8, "name": "somename8"},
{"id": 9, "name": "somename9"}
])
The statement is executed within the current transactional context of
this :class:`.Session`. The :class:`.Connection` which is used
to execute the statement can also be acquired directly by
calling the :meth:`.Session.connection` method. Both methods use
a rule-based resolution scheme in order to determine the
:class:`.Connection`, which in the average case is derived directly
from the "bind" of the :class:`.Session` itself, and in other cases
can be based on the :func:`.mapper`
and :class:`.Table` objects passed to the method; see the
documentation for :meth:`.Session.get_bind` for a full description of
this scheme.
The :meth:`.Session.execute` method does *not* invoke autoflush.
The :class:`.ResultProxy` returned by the :meth:`.Session.execute`
method is returned with the "close_with_result" flag set to true;
the significance of this flag is that if this :class:`.Session` is
autocommitting and does not have a transaction-dedicated
:class:`.Connection` available, a temporary :class:`.Connection` is
established for the statement execution, which is closed (meaning,
returned to the connection pool) when the :class:`.ResultProxy` has
consumed all available data. This applies *only* when the
:class:`.Session` is configured with autocommit=True and no
transaction has been started.
:param clause:
An executable statement (i.e. an :class:`.Executable` expression
such as :func:`.expression.select`) or string SQL statement
to be executed.
:param params:
Optional dictionary, or list of dictionaries, containing
bound parameter values. If a single dictionary, single-row
execution occurs; if a list of dictionaries, an
"executemany" will be invoked. The keys in each dictionary
must correspond to parameter names present in the statement.
:param mapper:
Optional :func:`.mapper` or mapped class, used to identify
the appropriate bind. This argument takes precedence over
``clause`` when locating a bind. See :meth:`.Session.get_bind`
for more details.
:param bind:
Optional :class:`.Engine` to be used as the bind. If
this engine is already involved in an ongoing transaction,
that connection will be used. This argument takes
precedence over ``mapper`` and ``clause`` when locating
a bind.
:param \**kw:
Additional keyword arguments are sent to :meth:`.Session.get_bind()`
to allow extensibility of "bind" schemes.
.. seealso::
:ref:`sqlexpression_toplevel` - Tutorial on using Core SQL
constructs.
:ref:`connections_toplevel` - Further information on direct
statement execution.
:meth:`.Connection.execute` - core level statement execution
method, which is :meth:`.Session.execute` ultimately uses
in order to execute the statement.
RË RÌ N( R t _literal_as_textR RK RL Rj R« ( R? RË t paramsRÍ RO RÎ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR« È s
{ c K s( | j | d | d | d | | j S( s: Like :meth:`~.Session.execute` but return a scalar result.RÐ RÍ RO ( R« R¶ ( R? RË RÐ RÍ RO RÎ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR¶ K s c C s | j d t d S( s> 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.
R N( t _close_implR¤ ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR Q s
c C s | j d t d S( sð Close this Session, using connection invalidation.
This is a variant of :meth:`.Session.close` that will additionally
ensure that the :meth:`.Connection.invalidate` method will be called
on all :class:`.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
R N( RÑ Rj ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR ] s c C sG | j | j d k rC x' | j j D] } | j | q) Wn d S( N( R¯ R
R RU R ( R? R R
( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRÑ ~ s
c C sV x. | j j t | j D] } | j q W| j | _ i | _ i | _ d S( s Remove all object instances from this ``Session``.
This is equivalent to calling ``expunge(obj)`` on all objects in this
``Session``.
N( Re Rk Rv RV Rw R¸ RW ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR¯ s
# c C sÆ y t | } WnF t j k
rX t | t sH t j d | q | | j | <nj X| j rr | | j | <nP | j r¯ | | j | j <x4 | j
D] } | | j | <q Wn t j d | d S( Ns! Not an acceptable bind target: %s( R
R9 t NoInspectionAvailableR| R t
ArgumentErrorR» t
is_selectablet is_mappert class_t _all_tables( R? Rc RO t inspt
selectable( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRÄ s c C s | j | | d S( sÓ Associate a :class:`.Mapper` with a "bind", e.g. a :class:`.Engine`
or :class:`.Connection`.
The given mapper is added to a lookup used by the
:meth:`.Session.get_bind` method.
N( RÄ ( R? RÍ RO ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt bind_mapperª s c C s | j | | d S( sÒ Associate a :class:`.Table` with a "bind", e.g. a :class:`.Engine`
or :class:`.Connection`.
The given mapper is added to a lookup used by the
:meth:`.Session.get_bind` method.
N( RÄ ( R? t tableRO ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt
bind_table´ s c C sò | | k o d k n r> | j r, | j St j d n | d k r y t | } Wq t j k
r t | t r t j | q q Xn | j
r?| ró x. | j j D] } | | j
k r´ | j
| Sq´ W| d k ró | j
} qó n | d k r?x: t j | d t D] } | | j
k r| j
| SqWq?n | j rO| j St | t j j rt| j rt| j S| r| j
j r| j
j Sg } | d k r¶| j d | n | d k rÒ| j d n t j d d j | d S( s< Return a "bind" to which this :class:`.Session` is bound.
The "bind" is usually an instance of :class:`.Engine`,
except in the case where the :class:`.Session` has been
explicitly bound directly to a :class:`.Connection`.
For a multiply-bound or unbound :class:`.Session`, the
``mapper`` or ``clause`` arguments are used to determine the
appropriate bind to return.
Note that the "mapper" argument is usually present
when :meth:`.Session.get_bind` is called via an ORM
operation such as a :meth:`.Session.query`, each
individual INSERT/UPDATE/DELETE operation within a
:meth:`.Session.flush`, call, etc.
The order of resolution is:
1. if mapper given and session.binds is present,
locate a bind based on mapper.
2. if clause given and session.binds is present,
locate a bind based on :class:`.Table` objects
found in the given clause present in session.binds.
3. if session.bind is present, return that.
4. if clause given, attempt to return a bind
linked to the :class:`.MetaData` ultimately
associated with the clause.
5. if mapper given, attempt to return a bind
linked to the :class:`.MetaData` ultimately
associated with the :class:`.Table` or other
selectable to which the mapper is mapped.
6. No bind can be found, :exc:`~sqlalchemy.exc.UnboundExecutionError`
is raised.
:param mapper:
Optional :func:`.mapper` mapped class or instance of
:class:`.Mapper`. The bind can be derived from a :class:`.Mapper`
first by consulting the "binds" map associated with this
:class:`.Session`, and secondly by consulting the :class:`.MetaData`
associated with the :class:`.Table` to which the :class:`.Mapper`
is mapped for a bind.
:param clause:
A :class:`.ClauseElement` (i.e. :func:`~.sql.expression.select`,
:func:`~.sql.expression.text`,
etc.). If the ``mapper`` argument is not present or could not
produce a bind, the given expression construct will be searched
for a bound element, typically a :class:`.Table` associated with
bound :class:`.MetaData`.
sl This session is not bound to a single Engine or Connection, and no context was provided to locate a binding.t include_cruds mapper %ss SQL expressions8 Could not locate a bind configured on %s or this Sessions , N( R RO R9 t UnboundExecutionErrorR
RÒ R| R R t UnmappedClassErrorR» RÖ t __mro__t mapped_tablet sql_utilt find_tablesRj R R t
ClauseElementt appendt join( R? RÍ RË R! R t context( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRK ¾ sJ 5
c O s | j | | | S( sT Return a new :class:`.Query` object corresponding to this
:class:`.Session`.( RÀ ( R? t entitiesR' ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR % s c c s$ | j } t | _ | V| | _ d S( s 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.
.. versionadded:: 0.7.6
N( R¿ R¤ ( R? R¿ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt no_autoflush+ s c C s[ | j rW | j rW y | j WqW t j k
rS } | j d t j | qW Xn d S( Ns raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely( R¿ RZ R[ R9 t StatementErrort
add_detailR t raise_from_cause( R? t e( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt
_autoflushG s c C s¥ y t j | } Wn# t j k
r8 t j | n X| j | | t j | j t | | j
d | d | d | d k r¡ t j
d t | n d S( sX 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 lockmode: Passed to the :class:`~sqlalchemy.orm.query.Query`
as used by :meth:`~sqlalchemy.orm.query.Query.with_lockmode`.
.. seealso::
:ref:`session_expire` - introductory material
:meth:`.Session.expire`
:meth:`.Session.expire_all`
t
refresh_statet lockmodet only_load_propss Could not refresh instance '%s'N( R t instance_stateR t NO_STATEt UnmappedInstanceErrort
_expire_stateR t
load_on_identR R Rc R R9 R: R ( R? R) t attribute_namesRð R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRµ V s $c C s7 x0 | j j D] } | j | j | j j q Wd S( s´ 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`
N( Re Rk Rm Rn Ro ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR s c C sM y t j | } Wn# t j k
r8 t j | n X| j | | d S( s 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`
N( R Rò R Ró Rô Rõ ( R? R) R÷ R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR¬ « s
#c C s | j | | r) | j | j | nU t | j j j d | } | j | x' | D] \ } } } } | j | q[ Wd S( Ns refresh-expire( t _validate_persistentt _expire_attributesRn Rv t managerRÍ t cascade_iteratort _conditional_expire( R? R R÷ t cascadedt ot mt st_t dct_( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRõ Ô s
c C sU | j r% | j | j | j j n, | | j k rQ | j j | | j n d S( s5 Expire a state if persistent, else expunge if pendingN( Rc Rm Rn Re Ro RV t popRw ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRü á s
s 0.7sB The non-weak-referencing identity map feature is no longer needed.c C s
| j j S( s 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.
( Re t prune( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR ê s
c C sÀ y t j | } Wn# t j k
r8 t j | n X| j | j k rg t j d t | n t
| j j j
d | } | j | x' | D] \ } } } } | j | q Wd S( sà Remove the `instance` from this ``Session``.
This will free all internal references to the instance. Cascading
will be applied according to the *expunge* cascade rule.
s* Instance %s is not present in this SessionR® N( R Rò R Ró Rô R R¾ R9 R: R Rv Rú RÍ Rû Rb ( R? R) R Rý Rþ Rÿ R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR® ù s
c C s | | j k r, | j j | | j nn | j j | rn | j j | | j j | d | j n, | j r | j j j | d | j n d S( N( RV R Rw Re t contains_stateRf RW R R
( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRb s
c C s x.| D]&} t | } | j } | d k r | j | } t j | d r] | j sp t j | d r t j d t
| n | j d k r§ | | _ ns | j | k r| j j
| | | j j k rï | j j | d } n | j } | | f | j j | <| | _ n | j j | q q Wt j j d | D | j | j | x0 t | j | j D] } | j j | qwWd S( Ni sN Instance %s has a NULL identity key. If this is an auto-generated value, check that the database table allows generation of new primary key values, and that the mapped Column object is configured to expect these generated values. Ensure also that this flush() is not occurring at an inappropriate time, such aswithin a load() event.i c s s | ] } | | j f Vq d S( N( Rn ( t .0R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pys <genexpr>E s ( R t objR t _identity_key_from_stateR t intersectiont allow_partial_pkst
issupersetR R R Rc Re Rf R
RY Rg t statelibt
InstanceStatet _commit_all_statest _register_alteredR` RV R ( R? t statesR RÍ R t instance_keyt orig_key( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _register_newly_persistent s6
c C s\ | j rX | j rX xC | D]8 } | | j k rA t | j j | <q t | j j | <q Wn d S( N( R; R
RV Rj RX ( R? R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR N s
c C sf x_ | D]W } | j r2 | j r2 t | j j | <n | j j | | j j | d t | _ q Wd S( N( R; R
Rj RW Re Rf R R Rh ( R? R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt _remove_newly_deletedV s
c C si | r | j r | j d n y t j | } Wn# t j k
rW t j | n X| j | d S( sñ Place 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()``.
s
Session.add()N( R¼ t _flush_warningR Rò R Ró Rô t _save_or_update_state( R? R) t _warnR ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR¨ _ s
c C sA | j r | j d n x! | D] } | j | d t q Wd S( s: Add the given collection of instances to this ``Session``.s Session.add_all()R N( R¼ R R¨ R¤ ( R? t instancesR) ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR© s s
c C s\ | j | t | } x< | j d | d | j D] \ } } } } | j | q5 Wd S( Ns save-updatet halt_on( t _save_or_update_implR Rû t _contains_state( R? R RÍ Rþ Rÿ R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR | s
c C s | j r | j d n y t j | } Wn# t j k
rQ t j | n X| j d k r} t j
d t | n | | j k r d S| j
| d t t | j j j d | } | j | j | <| j j | x' | D] \ } } } } | j | që Wd S( sf Mark an instance as deleted.
The database delete operation occurs upon ``flush()``.
s Session.delete()s Instance '%s' is not persistedNt include_beforeRª ( R¼ R R Rò R Ró Rô Rc R R9 R: R RW t _attachRj Rv Rú RÍ Rû R Re R¨ t _delete_impl( R? R) R t cascade_statesRþ Rÿ R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRª s& c C s | j r | j d n i } | r2 | j n t | | j } z; t | _ | j t j | t j | d | d | SWd | | _ Xd S( sS 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.
: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.
s Session.merge()t loadt
_recursiveN(
R¼ R Rî R R¿ R¤ t _mergeR Rò t
instance_dict( R? R) R R R¿ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR´ s -
c C s
t | } | | k r | | St } | j } | d k rx | sS t j d n | j | } t j | d k } n t } | | j
k r | j
| } n½ | sû | j r¾ t j d n | j j
} t j | }
| |
_ | j |
t } n_ | rTt j | d s2| j rTt j | d rT| j | j j | d } n d } | d k r©| j j
} t j | }
t j | } t } | j |
n t j | }
t j | } | | | <| |
k rÎ| j d k r| j | | | j d t j } | j |
| | j d t j }
| t j k r|
t j k r| |
k rt j d | t |
|
f qn | j |
_ | j! |
_! x3 | j" D]% } | j# | | | |
| | | q¢Wn | sê|
j$ | | j
n | r |
j% j& j' |
d n | S( Ns¦ merge() with load=False option does not support objects transient (i.e. unpersisted) objects. flush() all changes on mapped instances before merging with load=False.i s merge() with load=False option does not support objects marked as 'dirty'. flush() all changes on mapped instances before merging with load=False.t passives Version id '%s' on merged state %s does not match existing version '%s'. Leave the version attribute unset when merging to update the most recent version.(( R R¤ Rc R R9 R: R R t NEVER_SETRj Re Rl t
class_managert new_instanceRò Ri R R R R
R RÖ t getR" R t version_id_colt _get_state_attr_by_columnt PASSIVE_NO_INITIALIZEt PASSIVE_NO_RESULTR t StaleDataErrorR t load_patht load_optionst iterate_propertiesR´ t _commit_allRú R= R ( R? R t
state_dictR R RÍ R& Rc t key_is_persistentt mergedt merged_statet merged_dictt existing_versiont merged_versiont prop( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR! î s
"
c C s2 | j j | s. t j d t | n d S( Ns3 Instance '%s' is not persistent within this Session( Re R R9 R: R ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRø T s c C s | j d k r+ t j d t | n | j | | | j k ro | j | j | <t | j | _ n | j
| d S( NsG Object '%s' already has an identity - it can't be registered as pending( Rc R R9 R: R t _before_attachRV R t lent insert_orderR ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt
_save_implZ s
c C sÕ | j j | r% | | j k r% d S| j d k rP t j d t | n | j ru t j d t | n | j | d t
| j j | d | r´ | j j | n | j j
| | j | d S( Ns Instance '%s' is not persistedss Instance '%s' has been deleted. Use the make_transient() function to send this object back to the transient state.t check_identity_map( Re R RW Rc R R9 R: R Rh R9 R¤ R Rg R¨ R ( R? R R^ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRi f s" c C s0 | j d k r | j | n
| j | d S( N( Rc R R< Ri ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR ~ s c C s` | | j k r d S| j d k r& d S| j | d t | j | j | <| j j | d S( NR ( RW Rc R R Rj R Re R¨ ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR s c C s/ t j | } | j | d t t | _ d S( sÖ 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:`.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 values present on this
object - it follows that this functionality
generally only works for many-to-one-relationships.
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:`.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.
: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.
.. versionadded:: 0.8
.. seealso::
``load_on_pending`` at :func:`.relationship` - this flag
allows per-relationship loading of many-to-ones on items that
are pending.
R N( R Rò R Rj t
_load_pending( R? R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt enable_relationship_loading s 3c C sì | j | j k r: | j j r: | j j | | j n | r | j r | j | j k r | j j | r t j d t
| | j f n | j rè | j | j k rè | j t k rè t j d t
| | j | j f n d S( NsZ Can't attach instance %s; another instance with key %s is already present in this session.s> Object '%s' is already attached to session '%s' (this is '%s')( R R¾ R= t
before_attachR Rc Re R R9 R: R R ( R? R R= ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR9 Æ s c C s | j | j k r | r( | j | n | j | _ | j r^ | j d k r^ | j | _ n | j j r | j j | | j q n d S( N( R R¾ R9 Rl t _strong_objR R R= t after_attach( R? R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR Û s c C sF y t j | } Wn# t j k
r8 t j | n X| j | S( sª Return 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 Rò R Ró Rô R ( R? R) R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR¦ æ s
c C s, t t | j j t | j j S( sW Iterate over all pending or persistent instances within this
Session.
( t iterRv RV R Re ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR§ ó s c C s | | j k p | j j | S( N( RV Re R ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR û s c C sV | j r t j d n | j r+ d Sz t | _ | j | Wd t | _ Xd S( s® 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.
s Session is already flushingN( RZ R9 R: R Rj t _flushR¤ ( R? t objects( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR[ þ s c C s t j d | d S( NsÚ Usage 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{ ( R? t method( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR $ s c C s" | j j o! | j o! | j S( N( Re t check_modifiedRW RV ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR , s
c C s/ | j } | r8 | j r8 | j r8 | j j j d St | } | j j rr | j j | | | | j } n t | j } t | j } t | j
| } | rt } x] | D]L } y t j | } Wn# t
j k
rù t
j | n X| j | q» Wn d } t } | rG| j | j | j
| }
n | j | j
| }
xL |
D]D } t | j | o| j } | j | d | | j | qfW| rÏ| j | j
| }
n | j
| }
x! |
D] } | j | d t qåW| j sd S| j d t | _ } yÖ t | _ z | j Wd t | _ X| j j | | | j | rà| j j ràt! | j j }
t" j# j$ g | j j D] } | | j% f ^ q§d | j t& j' d |
n | j j( | | | j) Wn* t& j* | j+ d t Wd QXn Xd S( Nt isdeleteRÊ R" sÿ Attribute 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 (, t
_dirty_statesRW RV Re Ro Rx R R= t before_flushR` t
differenceR Rò R Ró Rô R¨ R Ra R R t
_is_orphant has_identityt register_objectRj t has_workR R
R¼ R« R¤ t after_flusht finalize_flush_changesR: R R R
Rn R R{ t after_flush_postexecR R R ( R? RE t dirtyt
flush_contextRh t newt objsetRþ R t processedt proct is_orphanR
t len_( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRD 1 sr
$
%
c C sV xO t j d | D d D]. \ \ } } } | j | | | t | | q Wd S( s
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`
**before using this method, and fully test and confirm the
functionality of all code developed using these systems.**
:param objects: a list 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.
.. seealso::
:ref:`bulk_operations`
:meth:`.Session.bulk_insert_mappings`
:meth:`.Session.bulk_update_mappings`
c s s | ] } t j | Vq d S( N( R Rò ( R R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pys <genexpr>â s c S s | j | j d k f S( N( RÍ Rc R ( R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt <lambda>ã s N( t itertoolst groupbyt _bulk_save_mappingsRj ( R? RE t return_defaultst update_changed_onlyRÍ t isupdateR ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR± s I
c C s | j | | t t | t d S( sè
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:`.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`
**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:`.Mapper` object,
representing the single kind of object represented within the mapping
list.
:param mappings: a list 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.
.. seealso::
:ref:`bulk_operations`
:meth:`.Session.bulk_save_objects`
:meth:`.Session.bulk_update_mappings`
N( R^ R¤ ( R? RÍ t mappingsR_ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR² é s ?c C s | j | | t t t t d S( s¶ 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`
**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:`.Mapper` object,
representing the single kind of object represented within the mapping
list.
:param mappings: a list 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`
N( R^ Rj R¤ ( R? RÍ Rb ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR³ + s /c C s² t | } t | _ | j d t } zz yI | rO t j | | | | | n t j | | | | | | j Wn* t j | j
d t Wd QXn XWd t | _ Xd S( NRÊ R ( R
Rj RZ R R t _bulk_updatet _bulk_insertR R R R R¤ ( R? RÍ Rb Ra t isstatesR_ R` R
( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR^ \ s"
c
C sª t | } | j s t S| j } x | j j D]o } | rN t | j d s/ t | j d rg q/ n | j j | | d t j \ } } } | s | r/ t
Sq/ Wt Sd S( s 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)
.. versionchanged:: 0.8
When using SQLAlchemy 0.7 and earlier, the ``passive``
flag should **always** be explicitly set to ``True``,
else SQL loads/autoflushes may proceed which can affect
the modified state itself:
``session.is_modified(someobject, passive=True)``\ .
In 0.8 and above, the behavior is corrected and
this flag is ignored.
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:
.. versionchanged:: 0.8
Ignored for backwards compatibility.
When using SQLAlchemy 0.7 and earlier, this flag should always
be set to ``True``.
t get_collectiont get_historyR# N( R Rl R¤ Rn Rú R t hasattrt implRg t NO_CHANGERj (
R? R) t include_collectionsR# R t dict_t attrt addedt unchangedRh ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR° t s C c C s | j o | j j S( s+ 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:`.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 is 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
RB ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRB Ï s 8c C s
| j j S( s« The set of all persistent states considered dirty.
This method returns all states that were modified including
those that were possibly deleted.
( Re RI ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRI
s c C s8 t j g | j D]! } | | j k r | j ^ q S( sZ 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.
( R t IdentitySetRI RW R ( R? R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRS !
s
c C s t j t | j j S( sD The set of all instances marked as 'deleted' within this ``Session``( R Rp Rv RW R ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRh >
s c C s t j t | j j S( sA The set of all instances marked as 'new' within this ``Session``.( R Rp Rv RV R ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRU D
s ( s __contains__s __iter__s adds add_alls begins begin_nesteds closes commits
connections deletes executes expires
expire_alls expunges expunge_alls flushs get_binds is_modifieds bulk_save_objectss bulk_insert_mappingss bulk_update_mappingss merges querys refreshs rollbacks scalarN(P R* R+ R, t public_methodsR Rj R¤ R t QueryRA t connection_callableR
R t memoized_propertyRÁ R R R R R RP RL R« R¶ R R RÑ R¯ RÄ RÚ RÜ RK R¥ t contextmanagerRé Rî Rµ R R¬ Rõ Rü t
deprecatedR R® Rb R R R R¨ R© R Rª R´ R! Rø R< Ri R R R? R9 R R¦ R§ R R[ R R RD R± R² R³ R^ R° RB Re RI RS Rh RU ( ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR . sª ¨ $ F
!
g 4 ! )
3
' Af 7
& hP B 1 Z:
c B sD e Z d Z d e e e e d d Z d Z d Z d Z
RS( s' 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` 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`.
c K si | | d <| | d <| | d <| | d <| d k rA | | d <n | | _ t | j | f i | _ d S( s8 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` 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 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.
RO R¿ R Ru RÁ N( R RÎ R R* RÖ ( R? RO RÖ R¿ R Ru RÁ RÎ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyRA y
s
c K s xo | j j D]^ \ } } | d k r^ d | k r^ | j } | j | d | | d <q | j | | q W| j | S( se 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Î Rd t copyRy t
setdefaultRÖ ( R? t local_kwt kt vt d( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt __call__£
s
c K s | j j | d S( s± (Re)configure the arguments for this sessionmaker.
e.g.::
Session = sessionmaker()
Session.configure(bind=create_engine('sqlite://'))
N( RÎ Ry ( R? t new_kw( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt configure·
s c C s9 d | j j | j j d j d | j j D f S( Ns %s(class_=%r,%s)s , c s s% | ] \ } } d | | f Vq d S( s %s=%rN( ( R Rz R{ ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pys <genexpr>Æ
s ( t __class__R* RÖ Ræ RÎ Rd ( R? ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt __repr__Â
s N( R* R+ R, R R Rj R¤ RA R} R R ( ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR K
s , ' c C sx t j | } t | } | r1 | j | n | j j | j rP | ` n | j rb | ` n | j rt | ` n d S( sM 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 Rò R Rb t expired_attributesRx t callablesRc Rh ( R) R Rq ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt make_transientÊ
s .
c C s t j | } | j s! | j r3 t j d n | j j | | _ | j rZ | ` n | j | j
| j | j
| j d S( s 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`
s Given object must be transientN(
R Rò R Rc R9 R: RÍ R Rh R0 Rn Rù t unloaded( R) R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt make_transient_to_detached
s c C sG y t j | } Wn# t j k
r8 t j | n Xt | Sd S( s¾ Return the :class:`.Session` to which the given instance belongs.
This is essentially the same as the :attr:`.InstanceState.session`
accessor. See that attribute for details.
N( R Rò R Ró Rô R ( R) R ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyR( 2 s
(5 R, R\ t R R R R R9 Râ R R R R R R t
inspectionR
t baseR R R
R R R R R R\ R t
unitofworkR R R R t __all__t WeakValueDictionaryR R t objectR t symbolR/ R0 R1 R2 R3 R R R R R R( t counterR½ ( ( ( sK /home/tvault/.virtenv/lib/python2.7/site-packages/sqlalchemy/orm/session.pyt <module> sJ ".: ÿ Øÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ % @ (