lmZddlm
Z
ddlmZdd
lmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddl m!Z!ddl m"Z"dd l m#Z#dd!l mZdd"l$m%Z%dd!l$mZ&ejNr<>dd#l m(Z(dd$l m)Z)dd%lm*Z*dd&lm+Z+dd'lm,Z,dd(lm-Z-dd)lm.Z.dd*lm/Z/dd+lm0Z0dd,lm1Z1dd-lm2Z2dd.lm3Z3dd/lm4Z4dd0lm5Z5dd1l6m7Z7dd2l8m9Z9dd3l:m;Z;dd4l#m<Z<dd5l=m>Z>dd6l=m?Z?dd7l=m@Z@dd8l$mAZAdd9lBmCZCdd:lDmEZEdd;lFmGZGdd<lFmHZHdd=lFmIZIdd>lJmKZKdd?lLmMZMdd@lLmNZNddAlLmOZOddBlPmQZQedCe<06>D<EFBFBD>ZRej<>ZTdEeUdF<ej<>ZVdGeUdH<GdI<64>dJee"j<>dK<00>ZXGdL<64>dMe<18>ZYGdN<64>dOe<1F>ZZGdP<64>dQeZ<65>Z[GdR<64>dSeZ<65>Z\GdT<64>dUe[<5B>Z]GdV<64>dWee#j<>e"j<>dK<00>Z_GdX<64>dYe#j<><00>Z`GdZ<64>d[e`e_<65>Zaeae__by)\zBDefines :class:`_engine.Connection` and :class:`_engine.Engine`.
$r}tj|||<01><00>d}~wwxYw)zConstruct a new Connection.NrF)<15>enginerI<00>raw_connectionrN<00>loaded_dbapi<70>ErrorrH<00>$_handle_dbapi_exception_noconnectionrQrS<00>_Connection__savepoint_seq<65>_Connection__in_begin<69>_Connection__can_reconnect<63>_allow_autobegin<69>_should_log_info<66>_echorK<00>_join<69>_has_eventsrO<00>engine_connect)<08>selfrU<00>
_log_debugzConnection._log_debug<75>sY<00><00><12>%<25>%<25><03><0E><19>'<27>l<EFBFBD>G<EFBFBD><0E>><3E>><3E><20>3<EFBFBD>#8<>#8<>8<>B<EFBFBD>|<7C><1C><20><04><0B><0B><1A><1A><20><20><17>5<>3<EFBFBD>5<>"<22>5rwc<01>><00>|jjdd<00>}|S)N<>schema_translate_map)rO<00>get)rcr|s rg<00>_schema_translate_mapz Connection._schema_translate_map<61>s(<00><00><11>#<23>#<23>'<27>'<27>(><3E><04>E<><1D>$<24>#rwc<01><><00>|j}|jjdd<02>}|r||vr|jr||S|S)ztReturn the schema name for the given schema item taking into
<01><00>yr<>r<>)rcr<>r<>r<>r<>r<>r<>r<>r<>r|r<><00>opts rg<00>execution_optionszConnection.execution_options<6E>s<00><00>rwc<01><00>yr<>r<><00>rcr<>s rgr<>zConnection.execution_options<6E>s<00><00>;>rwc<01><><00>|js|jjr|jj||<01>|jj|<01>|_|jj||<01>|S)a<>0Set non-SQL options for the connection which take effect
during execution.
This method modifies this :class:`_engine.Connection` **in-place**;
the return value is the same :class:`_engine.Connection` object
upon which the method is called. Note that this is in contrast
to the behavior of the ``execution_options`` methods on other
objects such as :meth:`_engine.Engine.execution_options` and
:meth:`_sql.Executable.execution_options`. The rationale is that many
such execution options necessarily modify the state of the base
DBAPI connection in any case so there is no feasible means of
keeping the effect of such an option localized to a "sub" connection.
.. versionchanged:: 2.0 The :meth:`_engine.Connection.execution_options`
method, in contrast to other objects with this method, modifies
the connection in-place without creating copy of it.
As discussed elsewhere, the :meth:`_engine.Connection.execution_options`
method accepts any arbitrary parameters including user defined names.
All parameters given are consumable in a number of ways including
by using the :meth:`_engine.Connection.get_execution_options` method.
See the examples at :meth:`_sql.Executable.execution_options`
and :meth:`_engine.Engine.execution_options`.
The keywords that are currently recognized by SQLAlchemy itself
include all those listed under :meth:`.Executable.execution_options`,
as well as others that are specific to :class:`_engine.Connection`.
:param compiled_cache: Available on: :class:`_engine.Connection`,
:class:`_engine.Engine`.
A dictionary where :class:`.Compiled` objects
will be cached when the :class:`_engine.Connection`
compiles a clause
expression into a :class:`.Compiled` object. This dictionary will
supersede the statement cache that may be configured on the
:class:`_engine.Engine` itself. If set to None, caching
is disabled, even if the engine has a configured cache size.
Note that the ORM makes use of its own "compiled" caches for
some operations, including flush operations. The caching
used by the ORM internally supersedes a cache dictionary
specified here.
:param logging_token: Available on: :class:`_engine.Connection`,
A dictionary mapping schema names to schema names, that will be
applied to the :paramref:`_schema.Table.schema` element of each
:class:`_schema.Table`
encountered when SQL or DDL expression elements
are compiled into strings; the resulting schema name will be
converted based on presence in the map of the original name.
.. seealso::
:ref:`schema_translating`
:param preserve_rowcount: Boolean; when True, the ``cursor.rowcount``
attribute will be unconditionally memoized within the result and
made available via the :attr:`.CursorResult.rowcount` attribute.
Normally, this attribute is only preserved for UPDATE and DELETE
statements. Using this option, the DBAPIs rowcount value can
be accessed for other kinds of statements such as INSERT and SELECT,
to the degree that the DBAPI supports these statements. See
:attr:`.CursorResult.rowcount` for notes regarding the behavior
of this attribute.
.. versionadded:: 2.0.28
.. seealso::
:meth:`_engine.Engine.execution_options`
:meth:`.Executable.execution_options`
:meth:`_engine.Connection.get_execution_options`
:ref:`orm_queryguide_execution_options` - documentation on all
ORM-specific execution options
)rarUrK<00> set_connection_execution_optionsrO<00>unionrIr<>s rgr<>zConnection.execution_optionss`<00><00>B<10><1B><1B>t<EFBFBD>{<7B>{<7B>6<>6<><10>M<EFBFBD>M<EFBFBD>:<3A>:<3A>4<EFBFBD><13>E<>"&<26>"9<>"9<>"?<3F>"?<3F><03>"D<><04><1F><0C><0C><0C>5<>5<>d<EFBFBD>C<EFBFBD>@<40><13>rwc<01><00>|jS)z<>Get the non-SQL options which will take effect during execution.
rwc<01><<00>|jduxr
|jS)z)Return True if this connection is closed.N<>rNr\r<>s rg<00>closedzConnection.closeds#<00><00><14>%<25>%<25><14>-<2D>J<>d<EFBFBD>6J<36>6J<36>2J<32>Jrwc<01>><00>|j}|duxr|jS)z<>Return True if this connection was invalidated.
This does not indicate whether or not the connection was
$r}|j
|dddd<01>Yd}~yd}~wwxYw)aVThe underlying DB-API connection managed by this Connection.
This is a SQLAlchemy connection-pool proxied connection
which then has the attribute
:attr:`_pool._ConnectionFairy.dbapi_connection` that refers to the
actual driver connection.
.. seealso::
:ref:`dbapi_connections`
N)rN<00>_revalidate_connectionr<00>PendingRollbackError<6F>ResourceClosedError<6F>
BaseException<6F>_handle_dbapi_exception<6F>rc<00>es rgrdzConnection.connection6s|<00><00><10>!<21>!<21>)<29>
H<01><1B>2<>2<>4<>4<><18>)<29>)<29>)<29><><18>,<2C>,<2C>c<EFBFBD>.E<>.E<>F<><16><15><20>
H<01><14>,<2C>,<2C>Q<EFBFBD><04>d<EFBFBD>D<EFBFBD>$<24>G<>G<><47>
H<01>s<00>*<00>,A5<03>A0<03>0A5c<01><><00>|jj}|<01>J<00>|jj|<01>S#t$r}|j|dddd<01>Yd}~yd}~wwxYw)a<>Return the current **actual** isolation level that's present on
the database within the scope of this connection.
This attribute will perform a live SQL operation against the database
in order to procure the current isolation level, so the value returned
is the actual level on the underlying DBAPI connection regardless of
how this state was set. This will be one of the four actual isolation
- set per :class:`_engine.Connection` isolation level
N)rd<00>dbapi_connectionrI<00>get_isolation_levelr<6C>r<>)rcr<>r<>s rgr<>zConnection.get_isolation_levelPsh<00><00>J<20>?<3F>?<3F>;<3B>;<3B><18><1F>+<2B>+<2B>+<2B> D<01><17><<3C><<3C>3<>3<>4D<34>E<>E<><45><1C> D<01><10>(<28>(<28><11>D<EFBFBD>$<24><04>d<EFBFBD>C<>C<><43> D<01>s<00>7<00> A<03>A<03>Ac<01>.<00>|jjS)a<>The initial-connection time isolation level associated with the
:class:`_engine.Dialect` in use.
This value is independent of the
:paramref:`.Connection.execution_options.isolation_level` and
- set per :class:`_engine.Connection` isolation level
)rI<00>default_isolation_levelr<6C>s rgr<>z"Connection.default_isolation_level|s<00><00>6<14>|<7C>|<7C>3<>3<>3rwc<01>R<00>tjd|j<00>dndzd<04><05><00>)NzfCan't reconnect until invalid %stransaction is rolled back. Please rollback() fully before proceedingz
rwc<01><><00>|jrS|jrG|j<00>|j<00>|jj<00>|_|jStjd<01><00>)N<>This Connection is closed) r\r<>rQr<>rUrVrNrr<>r<>s rgr<>z!Connection._revalidate_connection<6F>s^<00><00><0F><1F><1F>D<EFBFBD>$4<>$4<><13><20><20>,<2C><14>)<29>)<29>+<2B>%)<29>[<5B>[<5B>%?<3F>%?<3F>%A<>D<EFBFBD>"<22><17>)<29>)<29>)<29><11>%<25>%<25>&A<>B<>Brwc<01>.<00>|jjS)a<>Info dictionary associated with the underlying DBAPI connection
referred to by this :class:`_engine.Connection`, allowing user-defined
data to be associated with the connection.
The data here will follow along with the DBAPI connection including
after it is returned to the connection pool and used again
in subsequent instances of :class:`_engine.Connection`.
}|<02>J<00>|j
|<01>d|_y)a<>Invalidate the underlying DBAPI connection associated with
this :class:`_engine.Connection`.
An attempt will be made to close the underlying DBAPI connection
immediately; however if this operation fails, the error is logged
but not raised. The connection is then discarded whether or not
close() succeeded.
Upon the next use (where "use" typically means using the
:meth:`_engine.Connection.execute` method or similar),
this :class:`_engine.Connection` will attempt to
procure a new DBAPI connection using the services of the
:class:`_pool.Pool` as a source of connectivity (e.g.
a "reconnection").
If a transaction was in progress (e.g. the
:meth:`_engine.Connection.begin` method has been called) when
:meth:`_engine.Connection.invalidate` method is called, at the DBAPI
level all state associated with this transaction is lost, as
the DBAPI connection is closed. The :class:`_engine.Connection`
will not allow a reconnection to proceed until the
:class:`.Transaction` object is ended, by calling the
:meth:`.Transaction.rollback` method; until that point, any attempt at
continuing to use the :class:`_engine.Connection` will raise an
:class:`~sqlalchemy.exc.InvalidRequestError`.
This is to prevent applications from accidentally
continuing an ongoing transactional operations despite the
fact that the transaction has been lost due to an
invalidation.
The :meth:`_engine.Connection.invalidate` method,
just like auto-invalidation,
will at the connection pool level invoke the
:meth:`_events.PoolEvents.invalidate` event.
:param exception: an optional ``Exception`` instance that's the
reason for the invalidation. is passed along to event handlers
and logging functions.
.. seealso::
:ref:`pool_connection_invalidation`
Nr<4E>)r<>r<>rr<>r<>rN<00>
invalidate)rc<00> exceptionr<6E>s rgr<>zConnection.invalidate<74>sa<00><00>\<10><1B><1B><12><0F>;<3B>;<3B><15>)<29>)<29>*E<>F<>F<><0F>9<>9<>&*<2A>&<<3C>&<<3C>#<23>*<2A>6<>6<>6<>#<23>.<2E>.<2E>y<EFBFBD>9<>!%<25><04>rwc<01><><00>|jrtjd<01><00>|j}|<01>tjd<03><00>|j<00>y)a2Detach the underlying DB-API connection from its connection pool.
E.g.::
with engine.connect() as conn:
conn.detach()
conn.execute(text("SET search_path TO schema1, schema2"))
# work with connection
# connection is fully closed (since we used "with:", can
# also call .close())
This :class:`_engine.Connection` instance will remain usable.
When closed
(or exited from a context manager context as above),
the DB-API connection will be literally closed and not
returned to its originating pool.
This method can be used to insulate the rest of an application
from a modified state on a connection (such as a transaction
isolation level or similar).
r<>Nz&Can't detach an invalidated Connection)r<>rr<>rN<00>InvalidRequestError<6F>detachr<68>s rgr<>zConnection.detach<63>sS<00><00>4<10>;<3B>;<3B><15>)<29>)<29>*E<>F<>F<>"&<26>"8<>"8<><1F>"<22>*<2A><15>)<29>)<29>8<><0E><0E><20>&<26>&<26>(rwc<01>X<00>|jr|js|j<00>yyyr<>)r]r[<00>beginr<6E>s rg<00>
_autobeginzConnection._autobegins"<00><00><0F><20><20><14><1F><1F><10>J<EFBFBD>J<EFBFBD>L<EFBFBD>*9<> rwc<01>|<00>|j<00>t|<00>|_|jStjd<01><00>)a<>Begin a transaction prior to autobegin occurring.
The returned object is an instance of :class:`_engine.RootTransaction`.
This object represents the "scope" of the transaction,
which completes when either the :meth:`_engine.Transaction.rollback`
or :meth:`_engine.Transaction.commit` method is called; the object
also works as a context manager as illustrated above.
The :meth:`_engine.Connection.begin` method begins a
transaction that normally will be begun in any case when the connection
is first used to execute a statement. The reason this method might be
used would be to invoke the :meth:`_events.ConnectionEvents.begin`
event at a specific time, or to organize code within the scope of a
connection checkout in terms of context managed blocks, such as::
with engine.connect() as conn:
with conn.begin():
conn.execute(...)
conn.execute(...)
with conn.begin():
conn.execute(...)
conn.execute(...)
The above code is not fundamentally any different in its behavior than
the following code which does not use
:meth:`_engine.Connection.begin`; the below style is known
as "commit as you go" style::
with engine.connect() as conn:
conn.execute(...)
conn.execute(...)
conn.commit()
conn.execute(...)
conn.execute(...)
conn.commit()
From a database point of view, the :meth:`_engine.Connection.begin`
method does not emit any SQL or change the state of the underlying
DBAPI connection in any way; the Python DBAPI does not have any
concept of explicit transaction begin.
.. seealso::
:ref:`tutorial_working_with_transactions` - in the
:ref:`unified_tutorial`
:meth:`_engine.Connection.begin_nested` - use a SAVEPOINT
:meth:`_engine.Connection.begin_twophase` -
use a two phase /XID transaction
:meth:`_engine.Engine.begin` - context manager available from
:class:`_engine.Engine`
z<>This connection has already initialized a SQLAlchemy Transaction() object via begin() or autobegin; can't call begin() here unless rollback() or commit() is called first.)rQ<00>RootTransactionrr<>r<>s rgr<>zConnection.beginsB<00><00>@<10><1C><1C>$<24> /<2F><04> 5<>D<EFBFBD><1D><17>$<24>$<24>$<24><15>)<29>)<29>#<23><0E>rwc<01>P<00>|j<00>|j<00>t|<00>S)a<>Begin a nested transaction (i.e. SAVEPOINT) and return a transaction
except exc.IntegrityError: # catch for duplicate username
trans.rollback() # rollback to savepoint
# outer transaction continues
connection.execute(...)
If :meth:`_engine.Connection.begin_nested` is called without first
calling :meth:`_engine.Connection.begin` or
:meth:`_engine.Engine.begin`, the :class:`_engine.Connection` object
will "autobegin" the outer transaction first. This outer transaction
may be committed using "commit-as-you-go" style, e.g.::
with engine.connect() as connection: # begin() wasn't called
with connection.begin_nested(): # will auto-"begin()" first
connection.execute(...)
# savepoint is released
connection.execute(...)
# explicitly commit outer transaction
connection.commit()
# can continue working with connection here
.. versionchanged:: 2.0
:meth:`_engine.Connection.begin_nested` will now participate
in the connection "autobegin" behavior that is new as of
2.0 / "future" style connections in 1.4.
.. seealso::
:meth:`_engine.Connection.begin`
:ref:`session_begin_nested` - ORM support for SAVEPOINT
)rQr<><00>NestedTransactionr<6E>s rg<00>begin_nestedzConnection.begin_nestedes&<00><00>R<10><1C><1C>$<24><10>O<EFBFBD>O<EFBFBD><1D><20><14>&<26>&rwc<01><><00>|j<00>tjd<01><00>|<01>$|jjj<00>}t
||<01>S)a'Begin a two-phase or XA transaction and return a transaction
handle.
The returned object is an instance of :class:`.TwoPhaseTransaction`,
which in addition to the methods provided by
:class:`.Transaction`, also provides a
:meth:`~.TwoPhaseTransaction.prepare` method.
:param xid: the two phase transaction id. If not supplied, a
random id will be generated.
.. seealso::
:meth:`_engine.Connection.begin`
:meth:`_engine.Connection.begin_twophase`
zOCannot start a two phase transaction when a transaction is already in progress.)rQrr<>rUrI<00>
create_xid<EFBFBD>TwoPhaseTransaction)rc<00>xids rg<00>begin_twophasezConnection.begin_twophase<73>sT<00><00>(<10><1C><1C>(<28><15>)<29>)<29>*<2A><0E><0E><0F>;<3B><16>+<2B>+<2B>%<25>%<25>0<>0<>2<>C<EFBFBD>"<22>4<EFBFBD><13>-<2D>-rwc<01>R<00>|jr|jj<00>yy)aCommit the transaction that is currently in progress.
This method commits the current transaction if one has been started.
If no transaction was started, the method has no effect, assuming
the connection is in a non-invalidated state.
A transaction is begun on a :class:`_engine.Connection` automatically
whenever a statement is first executed, or when the
:meth:`_engine.Connection.begin` method is called.
.. note:: The :meth:`_engine.Connection.commit` method only acts upon
the primary database transaction that is linked to the
:class:`_engine.Connection` object. It does not operate upon a
SAVEPOINT that would have been invoked from the
:meth:`_engine.Connection.begin_nested` method; for control of a
SAVEPOINT, call :meth:`_engine.NestedTransaction.commit` on the
:class:`_engine.NestedTransaction` that is returned by the
N)rQ<00>commitr<74>s rgr<>zConnection.commit<69>s$<00><00>,<10><1C><1C><10><1D><1D>$<24>$<24>&<26>rwc<01>R<00>|jr|jj<00>yy)aYRoll back the transaction that is currently in progress.
This method rolls back the current transaction if one has been started.
If no transaction was started, the method has no effect. If a
transaction was started and the connection is in an invalidated state,
the transaction is cleared using this method.
A transaction is begun on a :class:`_engine.Connection` automatically
whenever a statement is first executed, or when the
:meth:`_engine.Connection.begin` method is called.
.. note:: The :meth:`_engine.Connection.rollback` method only acts
upon the primary database transaction that is linked to the
:class:`_engine.Connection` object. It does not operate upon a
SAVEPOINT that would have been invoked from the
:meth:`_engine.Connection.begin_nested` method; for control of a
SAVEPOINT, call :meth:`_engine.NestedTransaction.rollback` on the
:class:`_engine.NestedTransaction` that is returned by the
N)rQ<00>rollbackr<6B>s rgr<>zConnection.rollback<63>s$<00><00>.<10><1C><1C><10><1D><1D>&<26>&<26>(<28>rwc<01>L<00>|jjj|<00>Sr<>)rUrI<00>do_recover_twophaser<65>s rg<00>recover_twophasezConnection.recover_twophases<00><00><13>{<7B>{<7B>"<22>"<22>6<>6<>t<EFBFBD><<3C><rwc<01>T<00>|jjj|||<02><01>y<00>N)<01>recover)rUrI<00>do_rollback_twophase<73>rcr<>r<>s rg<00>rollback_preparedzConnection.rollback_prepareds!<00><00><0C><0B><0B><1B><1B>0<>0<><14>s<EFBFBD>G<EFBFBD>0<>Lrwc<01>T<00>|jjj|||<02><01>yr<>)rUrI<00>do_commit_twophaser<65>s rg<00>commit_preparedzConnection.commit_prepared s!<00><00><0C><0B><0B><1B><1B>.<2E>.<2E>t<EFBFBD>S<EFBFBD>'<27>.<2E>Jrwc<01>N<00>|jduxr|jjS<00>z,Return True if a transaction is in progress.N)rQ<00> is_activer<65>s rg<00>in_transactionzConnection.in_transactions$<00><00><13><20><20><04>,<2C>L<><14>1B<31>1B<31>1L<31>1L<31>Lrwc<01>N<00>|jduxr|jjSr<>)rSr<>r<>s rg<00>in_nested_transactionz Connection.in_nested_transactions+<00><00><11>$<24>$<24>D<EFBFBD>0<>
3<><14>(<28>(<28>2<>2<>
rwc<01>L<00>|j}|<01>tjd<01><00>|S)Nz"connection is not in a transaction)rQrr<><00>rc<00>transs rg<00>_get_required_transactionz$Connection._get_required_transaction"s)<00><00><14>!<21>!<21><05><10>=<3D><15>)<29>)<29>*N<>O<>O<><14>rwc<01>L<00>|j}|<01>tjd<01><00>|S)Nz)connection is not in a nested transaction)rSrr<>r<>s rg<00> _get_required_nested_transactionz+Connection._get_required_nested_transaction(s/<00><00><14>(<28>(<28><05><10>=<3D><15>)<29>)<29>;<3B><0E><0E><15>rwc<01><00>|jS)zaReturn the current root transaction in progress, if any.
.. versionadded:: 1.4
)rQr<>s rg<00>get_transactionzConnection.get_transaction0s<00><00><14><20><20> rwc<01><00>|jS)zcReturn the current nested transaction in progress, if any.
jj|j<00>d|_y#t$r}|j|dddd<00>Yd}~<02>+d}~wwxYw#d|_wxYw)Nz?BEGIN (implicit; DBAPI should not BEGIN due to autocommit mode)zBEGIN (implicit)TF)
r_r<>rvr[rarUrKr<>rI<00>do_beginrdr<>r<><00>rc<00>transactionr<6E>s rg<00>_begin_implzConnection._begin_implAs<><00><00><0F>:<3A>:<3A><13>,<2C>,<2C>.<2E><14><0E><0E>'<27><12>
r3|j
<00>r|jd<01>n|jd<02>|jjj|j<00>yy#t$r}|j|dddd<00>Yd}~yd}~wwxYw)NzVROLLBACK using DBAPI connection.rollback(), DBAPI should ignore due to autocommit mode<64>ROLLBACK)
rarUrKr<>r<>r_r<>rvrI<00>do_rollbackrdr<>r<>r<>s rg<00>_rollback_implzConnection._rollback_implWs<><00><00><0F><1B><1B>t<EFBFBD>{<7B>{<7B>6<>6<><10>M<EFBFBD>M<EFBFBD>"<22>"<22>4<EFBFBD>(<28><0F>9<>9<><13>z<EFBFBD>z<EFBFBD><17>0<>0<>2<><18>N<EFBFBD>N<EFBFBD>E<01><16>
/B;<00>; C#<03>C<03>C#c<01><><00>|js|jjr|jj|<00>|jr3|j<00>r|j
d<01>n|j
d<02>|jjj|j<00>y#t$r}|j|dddd<00>Yd}~yd}~wwxYw)NzRCOMMIT using DBAPI connection.commit(), DBAPI should ignore due to autocommit mode<64>COMMIT)rarUrKr<>r_r<>rvrI<00> do_commitrdr<>r<>r<>s rg<00>_commit_implzConnection._commit_implis<><00><00><0F><1B><1B>t<EFBFBD>{<7B>{<7B>6<>6<><10>M<EFBFBD>M<EFBFBD><20><20><14>&<26><0F>:<3A>:<3A><13>,<2C>,<2C>.<2E><14><0E><0E>A<01><12>
Ac<01><00>yr<>r<>r.s rg<00>scalarszConnection.scalars<00><00><00>rwc<01><00>yr<>r<>r.s rgr<zConnection.scalars(<00><00><00> rwc<01>F<00>|j|||<03><01>j<00>S)a<>Executes and returns a scalar result set, which yields scalar values
from the first column of each row.
This method is equivalent to calling :meth:`_engine.Connection.execute`
to receive a :class:`_result.Result` object, then invoking the
:meth:`_result.Result.scalars` method to produce a
d<03><00>|r|g}ng}||||fS)NrrzLEvent handler can't return non-empty multiparams and params at the same time)<06>lenrK<00>before_execute<74>listrr<>)rc<00>elem<65>distilled_paramsr<73>rSrT<00>fns rgrMz$Connection._invoke_before_exec_event
||| |<02>s<01>d }n|s|j4j=||| |<02>|js|jjr*|jj?|||| ||j<00>|jA<00>|jC<00>}
|
S#t$r)}|j|t|<03>|d|<02>Yd}~<06><03>7d}~wwxYw#t$r }|j||| ||<02>Yd}~
Sd}~wwxYw)zzcontinue the _execute_context() method for a single DBAPI
cursor.execute() or cursor.executemany() call.
Nr<00>[%s] %r<>
<00><02>batches<65>ismulti<74>8[%s] [SQL parameters hidden due to hide_parameters=True]Fr(Tr))"<22>bind_typingr<00>
SETINPUTSIZES<45>_prepare_set_input_sizes<65>do_set_input_sizes<65>cursorr<72>r<>r|r/r0<00>executemanyrarUrK<00>before_cursor_executer_rv<00>_get_cache_stats<74>hide_parameters<72>sql_util<69>_repr_paramsrr<00>EXECUTEMANYrrI<00>do_executemanyr<79><00>do_execute_no_params<6D>
"<22><0B>D<0E><16>$<24>$<24><0C>(@<40>(@<40>@<40>'+<2B>-<2D>/C<>(<12>$<24><18><<3C><<3C>+<2B>+<2B>"<22>l<EFBFBD>l<EFBFBD>3<>3<>B<>B<><02><1D>"<22>)<29>0<>#<23><1A>+/<2F>K<EFBFBD>!<21>C<01>#<23><18>L<EFBFBD>L<EFBFBD>/<2F>/<2F><1E>%<25>,<2C><1F><16>*<2A>g<EFBFBD>.C<>.C<><17><<3C><<3C>+<2B>+<2B>"<22>l<EFBFBD>l<EFBFBD>3<>3<>H<>H<><02><1D>f<EFBFBD>m<EFBFBD>W<EFBFBD>=<3D>*.<2E>K<EFBFBD>!<21>I<01>#<23><18>L<EFBFBD>L<EFBFBD>5<>5<><1E><0A>w<EFBFBD><16>(,<2C>.<2E>0D<30>(<12>$<24><18><<3C><<3C>+<2B>+<2B>"<22>l<EFBFBD>l<EFBFBD>3<>3<>><3E>><3E><02><1D>"<22>)<29>0<>#<23><1A>+/<2F>K<EFBFBD>!<21>?<3F>#<23><18>L<EFBFBD>L<EFBFBD>+<2B>+<2B><1E><0A>/C<>W<EFBFBD><16><14><1F><1F>4<EFBFBD>;<3B>;<3B>#:<3A>#:<3A><14><0A><0A>2<>2<><18><1A>!<21>(<28><1B><1B>'<27>'<27><12><14><1D><1D><1F><1C>0<>0<>2<>F<EFBFBD><16><0A><>s%<25><16><18>0<>0<><19>3<EFBFBD>y<EFBFBD>><3E>:<3A>t<EFBFBD>W<EFBFBD><16><16><><16><>h<1D><0E><10>(<28>(<28><11>=<3D>"6<><06><07><0E><0E><16><0A><><0E>sE<00>M<00>(A,N<00>A8N<00>A5N<00>BN<00> N <03>N<03>N <03> N5<03>N0<03>0N5c
<EFBFBD>| D]}|||||<02>s<01>n|j||||<02>|r*|jjC||||||jD<00>|s<02><01><>||
jFz
}<0C><01><>|jI<00>|r||_%|jM<00>}|S#t&$rI}|j)|t+j,|
j.<00>|
j0d|d<07><08>Yd}~<0E><02>d}~wwxYw#t&$r4}|j)|t+j,|<0F>|||d<07><08>Yd}~<0E><>d}~wwxYw#t&$r }|j)|||||<02>Yd}~Sd}~wwxYw)z<>continue the _execute_context() method for an "insertmanyvalues"
operation, which will invoke DBAPI
cursor.execute() one or more times with individual log and
<EFBFBD>f<0E><13><1D><1D><1F><20>$,<2C><07>!<21><1C>0<>0<>2<>F<EFBFBD><16><0A><>c%<25><16><18>0<>0<><19><20>0<>0<><19>1M<31>1M<31>N<>!<21>5<>5<><1C><1F>$(<28>1<><16><16><><16><>Z!<21><12><14>,<2C>,<2C><15><1C>,<2C>,<2C>X<EFBFBD>6<><1E><1A><1B> $<24>-<2D><12><12><><12><>><1D><0E><10>(<28>(<28><11>=<3D>"6<><06><07><0E><0E><16><0A><><0E>sN<00>'K4<02>M <02>/M <02> )N <00>4 M<05>=>M<05>M<05> N<05>*N<05>N<05> N2<03>N-<03>-N2c<01><><00>|js|jjr+|jjD]}||||||d<01>\}}<03>|jr#|j|<02>|jd|<03>|jjsdn|jjjD]}|||||<04>s<01>n|jj||||<04>|js|jjr!|jj|||||d<01>yy#t$r}|j|||||<04>Yd}~<06>gd}~wwxYw)a_Execute a statement + params on the given cursor.
Adds appropriate logging and exception handling.
This method is used by DefaultDialect for special-case
executions, such as for sequences and column defaults.
The path of statement execution in the majority of cases
<16>f<EFBFBD>i<EFBFBD><1A>W<EFBFBD>=<3D><19>6<><15><0C><0C>'<27>'<27><06><09>:<3A>w<EFBFBD>O<><10><1B><1B>t<EFBFBD>{<7B>{<7B>6<>6<><10>M<EFBFBD>M<EFBFBD>.<2E>.<2E><14>f<EFBFBD>i<EFBFBD><1A>W<EFBFBD>e<EFBFBD><0E> 7<><37><1D><0E><10>(<28>(<28><11>9<EFBFBD>j<EFBFBD>&<26>'<27><0E><0E><><0E>s<00>>AD*<00>!D*<00>* E<03>3E
<03>Ec<01><><00>|j<00>y#t$r4|jjjjdd<02><03>YywxYw)z\Close the given cursor, catching exceptions
$<0E><20>$(<28><20><17><08><12><1E><1E>&<26><11>$<24><16><17><14><14><14><14><14><1D>-<2D><1B><0E>C<EFBFBD><1E>&<26>&<26>3<>3<><02><1A><20><03>W<EFBFBD>F<EFBFBD><1D>)<29>;A<>A<><03>-<2D><08><>4<>$<24><0A><13>9J<39>9J<39>(J<><17>%<25>%<25><12>$<24>;<3B>m<EFBFBD><14><1A>)<29>)<29>(<28>1<EFBFBD>+<2B>6<>A<EFBFBD>=<3D><18>'<27>3<>3<>3<>&<26>5<>5<>h<EFBFBD>q<EFBFBD>k<EFBFBD>B<><01>I<><1B>A<EFBFBD>;<3B>*<2A>*<2A>*<2A><1A>1<EFBFBD>+<2B>,<2C>,<2C>X<EFBFBD>a<EFBFBD>[<5B>9<>9<><39>#!<21><1A>&<26>H<EFBFBD><19><><1A>s<00>F<02> F$<05>F<05>F$c<01>J<00>||j|fi|<03><01>j|<02>y)z<>run a DDL visitor.
This method is only here so that the MockConnection can change the
options given to the visitor so that "checkfirst" is skipped.
connection.execute(text("insert into x (a, b) values (1, 2)"))
trans.commit()
The object provides :meth:`.rollback` and :meth:`.commit`
methods in order to control transaction boundaries. It
also implements a context manager interface so that
the Python ``with`` statement can be used with the
:meth:`_engine.Connection.begin` method::
with connection.begin():
connection.execute(text("insert into x (a, b) values (1, 2)"))
The Transaction object is **not** threadsafe.
.. seealso::
:meth:`_engine.Connection.begin`
:meth:`_engine.Connection.begin_twophase`
:meth:`_engine.Connection.begin_nested`
.. index::
single: thread safety; Transaction
r<>Fr<46><00>_is_rootr<74>rHrdc<01><00>t<00><00>r<><00><01>NotImplementedError<6F>rcrds rgrhzTransaction.__init__<5F><00><00><00>!<21>#<23>#rwc<01><00>t<00><00>)z<>True if this transaction is totally deactivated from the connection
s<00><00><13>~<7E>~<7E>A<>d<EFBFBD>o<EFBFBD>o<EFBFBD>&A<>&A<>"A<>Arwc<01>h<00>|j<00>|jrJ<00>y#|jrJ<00>wxYw)a;Close this :class:`.Transaction`.
If this transaction is the base transaction in a begin/commit
nesting, the transaction will rollback(). Otherwise, the
method returns.
This is used to cancel a Transaction without affecting the scope of
an enclosing transaction.
N)rr<>r<>s rgr<>zTransaction.close
s0<00><00> &<26><10>N<EFBFBD>N<EFBFBD><1C><1B>~<7E>~<7E>%<25>%<25>~<7E><>t<EFBFBD>~<7E>~<7E>%<25>%<25>~<7E><><00>!<00>1c<01>h<00>|j<00>|jrJ<00>y#|jrJ<00>wxYw)a<>Roll back this :class:`.Transaction`.
The implementation of this may vary based on the type of transaction in
use:
* For a simple database transaction (e.g. :class:`.RootTransaction`),
it corresponds to a ROLLBACK.
* For a :class:`.NestedTransaction`, it corresponds to a
"ROLLBACK TO SAVEPOINT" operation.
* For a :class:`.TwoPhaseTransaction`, DBAPI-specific methods for two
phase transactions may be used.
N)rr<>r<>s rgr<>zTransaction.rollback
s2<00><00>" &<26><10><1D><1D><1F><1B>~<7E>~<7E>%<25>%<25>~<7E><>t<EFBFBD>~<7E>~<7E>%<25>%<25>~<7E>r#c<01>h<00>|j<00>|jrJ<00>y#|jrJ<00>wxYw)a<>Commit this :class:`.Transaction`.
The implementation of this may vary based on the type of transaction in
use:
* For a simple database transaction (e.g. :class:`.RootTransaction`),
it corresponds to a COMMIT.
* For a :class:`.NestedTransaction`, it corresponds to a
"RELEASE SAVEPOINT" operation.
* For a :class:`.TwoPhaseTransaction`, DBAPI-specific methods for two
4<><13>~<7E>~<7E><14>.<2E>.<2E>0<><13><EFBFBD><EFBFBD>2<>2<><14><0F><0F>3<>3<>;<3B>;<3B>=<3D><13>~<7E>~<7E><1E><14>0<>0<>2<><13><EFBFBD><EFBFBD>+<2B>+<2B>t<EFBFBD>3<>/3<><04><0F><0F>,<2C><17>><3E>><3E>!<21>!<21><13><EFBFBD><EFBFBD>+<2B>+<2B>4<EFBFBD>7<>7<>7<><37><14>~<7E>~<7E><1E><14>0<>0<>2<><13><EFBFBD><EFBFBD>+<2B>+<2B>t<EFBFBD>3<>/3<><04><0F><0F>,<2C>4<>s
<00>AC <00> A
size_alert<EFBFBD><01>echoflagr<67>)
r<>rcrI<00>logging_name<6D>echor<6F>r!<00>LRUCache<68>_lru_size_alertrmr <00>instance_logger<65>update_execution_options) rcr<>rIrcrhri<00>query_cache_sizer<65>r<>s rgrhzEngine.__init__<5F>s<><00><00><19><04><09><16><04><08><1E><04><0C><17> ,<2C>D<EFBFBD><1D><18><04><09>.<2E><04><1C><1B>q<EFBFBD><20>#'<27>=<3D>=<3D><20>T<EFBFBD>-A<>-A<>$<0E>D<EFBFBD><20>$(<28>D<EFBFBD><20><0B><1B><1B>D<EFBFBD>4<EFBFBD>0<><1C>)<29>D<EFBFBD>)<29>)<29>><3E>,=<3D>><3E>rwc<01><><00>|j<00>r1|jjdt|<01>|j<00>yy)NziCompiled cache size pruning from %d items to %d. Increase cache size to reduce the frequency of pruning.)r^rorpra<00>capacity)rc<00>caches rgrkzEngine._lru_size_alert<72>s9<00><00><0F><20><20>"<22><10>K<EFBFBD>K<EFBFBD><1C><1C>J<01><13>E<EFBFBD>
<EFBFBD><15><0E><0E><0E>#rwc<01><00>|S)z<>Returns this :class:`.Engine`.
Used for legacy schemes that accept :class:`.Connection` /
:class:`.Engine` objects within the same variable.
r<>r<>s rgrUz
Engine.engine<6E>s <00><00><14>rwc<01>R<00>|jr|jj<00>yy)a<>Clear the compiled cache associated with the dialect.
This applies **only** to the built-in cache that is established
via the :paramref:`_engine.create_engine.query_cache_size` parameter.
It will not impact any dictionary caches that were passed via the
N)rm<00>clearr<72>s rg<00>clear_compiled_cachezEngine.clear_compiled_cache<68>s$<00><00><10><1F><1F><10><20><20>&<26>&<26>(<28> rwc<01><><00>|jj||<01>|jj|<01>|_|jj||<01>y)a<>Update the default execution_options dictionary
of this :class:`_engine.Engine`.
The given keys/values in \**opt are added to the
default execution options that will be used for
all connections. The initial contents of this dictionary
can be sent via the ``execution_options`` parameter
to :func:`_sa.create_engine`.
.. seealso::
:meth:`_engine.Connection.execution_options`
:meth:`_engine.Engine.execution_options`
N)rK<00>set_engine_execution_optionsrOr<>rIr<>s rgrmzEngine.update_execution_options<6E>sE<00><00>"<0A><0A><0A>2<>2<>4<EFBFBD><13>=<3D>"&<26>"9<>"9<>"?<3F>"?<3F><03>"D<><04><1F><0C><0C><0C>1<>1<>$<24><03><rw.)r<>r<>r<>r<>r|c<01><00>yr<>r<>)rcr<>r<>r<>r<>r|r<>s rgr<>zEngine.execution_options<6E>s<00><00>rwc<01><00>yr<>r<>r<>s rgr<>zEngine.execution_options<6E>s<00><00>=@rwc<01>&<00>|j||<01>S)aReturn a new :class:`_engine.Engine` that will provide
:class:`_engine.Connection` objects with the given execution options.
The returned :class:`_engine.Engine` remains related to the original
:class:`_engine.Engine` in that it shares the same connection pool and
other state:
* The :class:`_pool.Pool` used by the new :class:`_engine.Engine`
is the
same instance. The :meth:`_engine.Engine.dispose`
method will replace
the connection pool instance for the parent engine as well
as this one.
* Event listeners are "cascaded" - meaning, the new
:class:`_engine.Engine`
inherits the events of the parent, and new events can be associated
with the new :class:`_engine.Engine` individually.
* The logging configuration and logging_name is copied from the parent
:class:`_engine.Engine`.
The intent of the :meth:`_engine.Engine.execution_options` method is
to implement schemes where multiple :class:`_engine.Engine`
objects refer to the same connection pool, but are differentiated
by options that affect some execution-level behavior for each
engine. One such example is breaking into separate "reader" and
"writer" :class:`_engine.Engine` instances, where one
:class:`_engine.Engine`
has a lower :term:`isolation level` setting configured or is even
transaction-disabled using "autocommit". An example of this
configuration is at :ref:`dbapi_autocommit_multiple`.
Another example is one that
uses a custom option ``shard_id`` which is consumed by an event
to change the current schema on a database connection::
then interprets this execution option to emit a MySQL ``use`` statement
to switch databases before a statement execution, while at the same
time keeping track of which database we've established using the
:attr:`_engine.Connection.info` dictionary.
.. seealso::
:meth:`_engine.Connection.execution_options`
- update execution options
on a :class:`_engine.Connection` object.
:meth:`_engine.Engine.update_execution_options`
- update the execution
options for a given :class:`_engine.Engine` in place.
:meth:`_engine.Engine.get_execution_options`
)rbr<>s rgr<>zEngine.execution_options<6E>s<00><00>\<14><1F><1F><04>c<EFBFBD>*<2A>*rwc<01><00>|jS)z<>Get the non-SQL options which will take effect during execution.
.. versionadded: 1.3
.. seealso::
:meth:`_engine.Engine.execution_options`
r<>r<>s rgr<>zEngine.get_execution_options7r<>rwc<01>.<00>|jjS)zsString name of the :class:`~sqlalchemy.engine.interfaces.Dialect`
in use by this :class:`Engine`.
)rIr<>r<>s rgr<>zEngine.nameBs<00><00><14>|<7C>|<7C><20><20> rwc<01>.<00>|jjS)zsDriver name of the :class:`~sqlalchemy.engine.interfaces.Dialect`
in use by this :class:`Engine`.
)rI<00>driverr<72>s rgr~z
Engine.driverKs<00><00><14>|<7C>|<7C>"<22>"<22>"rwc<01>"<00>d|j<00>d<02>S)NzEngine(r<>)rcr<>s rg<00>__repr__zEngine.__repr__Vs<00><00>#<23>x<EFBFBD>x<EFBFBD>)<29>)rwc<01><><00>|r|jj<00>|jj<00>|_|jj |<00>y)aDispose of the connection pool used by this
:class:`_engine.Engine`.
A new connection pool is created immediately after the old one has been
disposed. The previous connection pool is disposed either actively, by
closing out all currently checked-in connections in that pool, or
passively, by losing references to it but otherwise not closing any
connections. The latter strategy is more appropriate for an initializer
in a forked Python process.
:param close: if left at its default of ``True``, has the
effect of fully closing all **currently checked in**
database connections. Connections that are still checked out
will **not** be closed, however they will no longer be associated
with this :class:`_engine.Engine`,
so when they are closed individually, eventually the
:class:`_pool.Pool` which they are associated with will
be garbage collected and they will be closed out fully, if
not already closed on checkin.
If set to ``False``, the previous connection pool is de-referenced,
and otherwise not touched in any way.
.. versionadded:: 1.4.33 Added the :paramref:`.Engine.dispose.close`
parameter to allow the replacement of a connection pool in a child
process without interfering with the connections used by the parent
<EFBFBD><20><1E><1D><1C><20><1E>s<00>4<01>(<03>4<01>1<07>4c#<01><>K<00>|j<00>5}|j<00>5|<01><03>ddd<01>ddd<01>y#1swY<00>xYw#1swYyxYw<01>w)aReturn a context manager delivering a :class:`_engine.Connection`
with a :class:`.Transaction` established.
E.g.::
with engine.begin() as conn:
conn.execute(text("insert into table (x, y, z) values (1, 2, 3)"))
conn.execute(text("my_special_procedure(5)"))
Upon successful operation, the :class:`.Transaction`
is committed. If an error is raised, the :class:`.Transaction`
is rolled back.
.. seealso::
:meth:`_engine.Engine.connect` - procure a
:class:`_engine.Connection` from
an :class:`_engine.Engine`.
:meth:`_engine.Connection.begin` - start a :class:`.Transaction`
<EFBFBD><1E><1C>^<5E><1D><1C><><1C>^<5E>s.<00>A<01>A<03>:<05>A<03> A<01>A<09>A<03>A<07>Ac<01>v<00>|j<00>5}|j||fi|<03><01>ddd<00>y#1swYyxYwr<>)r<>r<>)rcr<>r<>r<>r+s rgr<>zEngine._run_ddl_visitor<6F>s0<00><00><12>Z<EFBFBD>Z<EFBFBD>\<5C>T<EFBFBD>!<21>D<EFBFBD>!<21>!<21>/<2F>7<EFBFBD>E<>f<EFBFBD>E<><1A>\<5C>\<5C>s<00>/<03>8c<01>$<00>|j|<00>S)a<Return a new :class:`_engine.Connection` object.
The :class:`_engine.Connection` acts as a Python context manager, so
the typical use of this method looks like::
with engine.connect() as connection:
connection.execute(text("insert into table values ('foo')"))
connection.commit()
Where above, after the block is completed, the connection is "closed"
and its underlying DBAPI resources are returned to the connection pool.
This also has the effect of rolling back any transaction that
was explicitly begun or was begun via autobegin, and will
emit the :meth:`_events.ConnectionEvents.rollback` event if one was
started and is still in progress.
.. seealso::
:meth:`_engine.Engine.begin`
)r`r<>s rgr<>zEngine.connect<63>s<00><00>.<14>#<23>#<23>D<EFBFBD>)<29>)rwc<01>6<00>|jj<00>S)aCReturn a "raw" DBAPI connection from the connection pool.
The returned object is a proxied version of the DBAPI
connection object used by the underlying driver in use.
The object will have all the same behavior as the real DBAPI
connection, except that its ``close()`` method will result in the
connection being returned to the pool, rather than being closed
for real.
This method provides direct DBAPI connection access for
special situations when the API provided by
:class:`_engine.Connection`
is not needed. When a :class:`_engine.Connection` object is already
present, the DBAPI connection is available using
the :attr:`_engine.Connection.connection` accessor.
