+hddlmZddlZddlZddlmZddlmZddlmZddlm Z ddlm Z d d l m Z d d l m Z d d l mZd d l mZd dlmZd d lmZ ej$ZGddeZGddeZGdde ZGddeZGddeZGddeZGddeZGddeej6ZGdd eZGd!d"eeZee_ y)#)with_statementN) Connectable)ExceptionContext)_distill_params)_distill_params_20)TransactionalContext)exc) inspection)log)util)compilerceZdZdZdZdZdZ dNdZejdZ dZ dZ e d Zd Zd Zd Zd ZdZdZdZe dZe dZe dZdZe dZdZdZe dZe dZej>ddOdZ dPdZ!dZ"dZ#dZ$d Z%dPd!Z&d"Z'dOd#Z(dOd$Z)d%Z*d&Z+d'Z,d(Z-d)Z.d*Z/d+Z0dOd,Z1dPd-Z2d.Z3d/Z4d0Z5d1Z6d2Z7d3Z8d4Z9d5Z:d6Z;d7Zd:Z?e@fd;ZAd<ZBd=ZCd>ZDe@fd?ZEd@ZFde@fdAZG dQdBZHdCZIdPdDZJdEZKdZLdZMdFZNeOdGZPdHZQejdIdJdKZSejdIdLdMZTy)R ConnectionaProvides high-level functionality for a wrapped DB-API connection. **This is the SQLAlchemy 1.x.x version** of the :class:`_engine.Connection` class. For the :term:`2.0 style` version, which features some API differences, see :class:`_future.Connection`. The :class:`_engine.Connection` object is procured by calling the :meth:`_engine.Engine.connect` method of the :class:`_engine.Engine` object, and provides services for execution of SQL statements as well as transaction control. The Connection object is **not** thread-safe. While a Connection can be shared among threads using properly synchronized access, it is still possible that the underlying DBAPI connection may not support shared access between threads. Check the DBAPI documentation for details. The Connection object represents a single DBAPI connection checked out from the connection pool. In this state, the connection pool has no affect upon the connection, including its expiration or timeout state. For the connection pool to properly manage connections, connections should be returned to the connection pool (i.e. ``connection.close()``) whenever the connection is not in use. .. index:: single: thread safety; Connection Fzsqlalchemy.engine.ConnectionNc ||_|j|_||_|rM|jJ||_||_|j |_d|_||_|j|_n||n|j|_dx|_ |_ d|_ d|_ ||_||_|jj|_|*|jj!|j|_|xs|duxr |j|_|rJ|j|_|js|jjr|jj#||duyy)zConstruct a new Connection.NFr)enginedialect_Connection__branch_from_dbapi_connection_execution_options_echoshould_close_with_resultdispatch _has_eventsraw_connection _transaction_nested_transaction_Connection__savepoint_seq_Connection__in_begin_Connection__can_reconnect_should_log_info_joinengine_connect) selfr connectionclose_with_result _branch_fromr _dispatchr_allow_revalidates I/var/www/html/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py__init__zConnection.__init__Cse ~~ ) --5 55%/D "&8D #%++DJ,1D )%DM+77D )**,  " <@ ?D  8#$D #DO,=D )#4D 557DJ"!% 3 3FOO D * t#:(:(:  * ))&,&?&?D #   t{{66 MM ( (|4/G H 7cJd|jvr|jdfdSy)N logging_tokencdd|S)N[z] )msgtokens r+z/Connection._message_formatter..~s E37r-r)r%r4s @r+_message_formatterzConnection._message_formatterzs* d55 5++O> 3#8#88B|  4#44r-c|j}|r||}tjrdtjz|d<|jj j |g|i|yr9)r7r r;r<rr=debugr?s r+ _log_debugzConnection._log_debugsY%% 'lG >> 3#8#88B|     535"5r-c:|jjddS)Nschema_translate_map)rgetr%s r+_schema_translate_mapz Connection._schema_translate_maps&&**+A4HHr-c|j}|jjdd}|r||vr|jr||S|S)ztReturn the schema name for the given schema item taking into account current schema translate map. rIN)schemarrJ_use_schema_map)r%objnamerIs r+schema_for_objectzConnection.schema_for_objectsP zz#66:: "D  !,,##'- -Kr-c|jj|j|j|jr |jn||j|j |j S)azReturn a new Connection which references this Connection's engine and connection; but does not have close_with_result enabled, and also whose close() method does nothing. .. deprecated:: 1.4 the "branching" concept will be removed in SQLAlchemy 2.0 as well as the "Connection.connect()" method which is the only consumer for this. The Core uses this very sparingly, only in the case of custom SQL default functions that are to be INSERTed as the primary key of a row where we need to get the value back, so we have to invoke it distinctly - this is a very uncommon case. Userland code accesses _branch() when the connect() method is called. The branched connection acts as much as possible like the parent, except that it stays connected when a close() event occurs. )r(rrr))r_connection_clsrrrrrrKs r+_branchzConnection._branchs\({{** KK  " "/3/A/A++t#66((mm +  r-c|jr|S|jj|j}|jj |_|S)z@define connection method chaining behavior for execution_options) _is_future __class____new____dict__copy)r%cs r+_generate_for_optionsz Connection._generate_for_optionssA ??K&&t~~6A++-AJHr-c|SNr2rKs r+ __enter__zConnection.__enter__s r-c$|jyr_)closer%type_value tracebacks r+__exit__zConnection.__exit__  r-c |j}|jj||_|js|jjr|j j |||jj |||S)a. Set non-SQL options for the connection which take effect during execution. For a "future" style connection, this method returns this same :class:`_future.Connection` object with the new options added. For a legacy connection, this method returns a copy of this :class:`_engine.Connection` which references the same underlying DBAPI connection, but also defines the given execution options which will take effect for a call to :meth:`execute`. As the new :class:`_engine.Connection` references the same underlying resource, it's usually a good idea to ensure that the copies will be discarded immediately, which is implicit if used as in:: result = connection.execution_options(stream_results=True).\ execute(stmt) Note that any key/value can be passed to :meth:`_engine.Connection.execution_options`, and it will be stored in the ``_execution_options`` dictionary of the :class:`_engine.Connection`. It is suitable for usage by end-user schemes to communicate with event listeners, for example. 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 autocommit: Available on: Connection, statement. When True, a COMMIT will be invoked after execution when executed in 'autocommit' mode, i.e. when an explicit transaction is not begun on the connection. Note that this is **library level, not DBAPI level autocommit**. The DBAPI connection will remain in a real transaction unless the "AUTOCOMMIT" isolation level is used. .. deprecated:: 1.4 The "autocommit" execution option is deprecated and will be removed in SQLAlchemy 2.0. See :ref:`migration_20_autocommit` for discussion. :param compiled_cache: Available on: Connection. 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`, :class:`_engine.Engine`. Adds the specified string token surrounded by brackets in log messages logged by the connection, i.e. the logging that's enabled either via the :paramref:`_sa.create_engine.echo` flag or via the ``logging.getLogger("sqlalchemy.engine")`` logger. This allows a per-connection or per-sub-engine token to be available which is useful for debugging concurrent connection scenarios. .. versionadded:: 1.4.0b2 .. seealso:: :ref:`dbengine_logging_tokens` - usage example :paramref:`_sa.create_engine.logging_name` - adds a name to the name used by the Python logger object itself. :param isolation_level: Available on: :class:`_engine.Connection`. Set the transaction isolation level for the lifespan of this :class:`_engine.Connection` object. Valid values include those string values accepted by the :paramref:`_sa.create_engine.isolation_level` parameter passed to :func:`_sa.create_engine`. These levels are semi-database specific; see individual dialect documentation for valid levels. The isolation level option applies the isolation level by emitting statements on the DBAPI connection, and **necessarily affects the original Connection object overall**, not just the copy that is returned by the call to :meth:`_engine.Connection.execution_options` method. The isolation level will remain at the given setting until the DBAPI connection itself is returned to the connection pool, i.e. the :meth:`_engine.Connection.close` method on the original :class:`_engine.Connection` is called, where an event handler will emit additional statements on the DBAPI connection in order to revert the isolation level change. .. warning:: The ``isolation_level`` execution option should **not** be used when a transaction is already established, that is, the :meth:`_engine.Connection.begin` method or similar has been called. A database cannot change the isolation level on a transaction in progress, and different DBAPIs and/or SQLAlchemy dialects may implicitly roll back or commit the transaction, or not affect the connection at all. .. note:: The ``isolation_level`` execution option is implicitly reset if the :class:`_engine.Connection` is invalidated, e.g. via the :meth:`_engine.Connection.invalidate` method, or if a disconnection error occurs. The new connection produced after the invalidation will not have the isolation level re-applied to it automatically. .. seealso:: :paramref:`_sa.create_engine.isolation_level` - set per :class:`_engine.Engine` isolation level :meth:`_engine.Connection.get_isolation_level` - view current actual level :ref:`SQLite Transaction Isolation ` :ref:`PostgreSQL Transaction Isolation ` :ref:`MySQL Transaction Isolation ` :ref:`SQL Server Transaction Isolation ` :ref:`session_transaction_isolation` - for the ORM :param no_parameters: When ``True``, if the final parameter list or dictionary is totally empty, will invoke the statement on the cursor as ``cursor.execute(statement)``, not passing the parameter collection at all. Some DBAPIs such as psycopg2 and mysql-python consider percent signs as significant only when parameters are present; this option allows code to generate SQL containing percent signs (and possibly other characters) that is neutral regarding whether it's executed by the DBAPI or piped into a script that's later invoked by command line tools. :param stream_results: Available on: Connection, statement. Indicate to the dialect that results should be "streamed" and not pre-buffered, if possible. For backends such as PostgreSQL, MySQL and MariaDB, this indicates the use of a "server side cursor" as opposed to a client side cursor. Other backends such as that of Oracle may already use server side cursors by default. The usage of :paramref:`_engine.Connection.execution_options.stream_results` is usually combined with setting a fixed number of rows to to be fetched in batches, to allow for efficient iteration of database rows while at the same time not loading all result rows into memory at once; this can be configured on a :class:`_engine.Result` object using the :meth:`_engine.Result.yield_per` method, after execution has returned a new :class:`_engine.Result`. If :meth:`_engine.Result.yield_per` is not used, the :paramref:`_engine.Connection.execution_options.stream_results` mode of operation will instead use a dynamically sized buffer which buffers sets of rows at a time, growing on each batch based on a fixed growth size up until a limit which may be configured using the :paramref:`_engine.Connection.execution_options.max_row_buffer` parameter. When using the ORM to fetch ORM mapped objects from a result, :meth:`_engine.Result.yield_per` should always be used with :paramref:`_engine.Connection.execution_options.stream_results`, so that the ORM does not fetch all rows into new ORM objects at once. For typical use, the :paramref:`_engine.Connection.execution_options.yield_per` execution option should be preferred, which sets up both :paramref:`_engine.Connection.execution_options.stream_results` and :meth:`_engine.Result.yield_per` at once. This option is supported both at a core level by :class:`_engine.Connection` as well as by the ORM :class:`_engine.Session`; the latter is described at :ref:`orm_queryguide_yield_per`. .. seealso:: :ref:`engine_stream_results` - background on :paramref:`_engine.Connection.execution_options.stream_results` :paramref:`_engine.Connection.execution_options.max_row_buffer` :paramref:`_engine.Connection.execution_options.yield_per` :ref:`orm_queryguide_yield_per` - in the :ref:`queryguide_toplevel` describing the ORM version of ``yield_per`` :param max_row_buffer: Available on: :class:`_engine.Connection`, :class:`_sql.Executable`. Sets a maximum buffer size to use when the :paramref:`_engine.Connection.execution_options.stream_results` execution option is used on a backend that supports server side cursors. The default value if not specified is 1000. .. seealso:: :paramref:`_engine.Connection.execution_options.stream_results` :ref:`engine_stream_results` :param yield_per: Available on: :class:`_engine.Connection`, :class:`_sql.Executable`. Integer value applied which will set the :paramref:`_engine.Connection.execution_options.stream_results` execution option and invoke :meth:`_engine.Result.yield_per` automatically at once. Allows equivalent functionality as is present when using this parameter with the ORM. .. versionadded:: 1.4.40 .. seealso:: :ref:`engine_stream_results` - background and examples on using server side cursors with Core. :ref:`orm_queryguide_yield_per` - in the :ref:`queryguide_toplevel` describing the ORM version of ``yield_per`` :param schema_translate_map: Available on: :class:`_engine.Connection`, :class:`_engine.Engine`, :class:`_sql.Executable`. :param schema_translate_map: Available on: Connection, Engine. 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. .. versionadded:: 1.1 .. seealso:: :ref:`schema_translating` .. seealso:: :meth:`_engine.Engine.execution_options` :meth:`.Executable.execution_options` :meth:`_engine.Connection.get_execution_options` )r]runionrrr set_connection_execution_optionsr)r%optr\s r+execution_optionszConnection.execution_optionssnz  & & ( 3399#>   t{{66 MM : :1c B 55a=r-c|jS)zGet the non-SQL options which will take effect during execution. .. versionadded:: 1.3 .. seealso:: :meth:`_engine.Connection.execution_options` r6rKs r+get_execution_optionsz Connection.get_execution_options&&&r-c<|jduxr |j S)z)Return True if this connection is closed.N)rr!rKs r+closedzConnection.closeds#%%-Jd6J6J2JJr-c|jr|jjS|jduxr |j S)z/Return True if this connection was invalidated.N)r invalidatedrrrrKs r+rtzConnection.invalidateds;   %%11 1%%-Adkk/Ar-c|j |jS|jS#tjtjf$rt $r}|j |ddddYd}~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)r_revalidate_connectionr PendingRollbackErrorResourceClosedError BaseException_handle_dbapi_exceptionr%es r+r&zConnection.connections|  ! ! ) H2244 )) ) ,,c.E.EF   H,,QdD$GG Hs*,A5A00A5c |jj|jS#t$r}|j |ddddYd}~yd}~wwxYw)aReturn 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 modes ``READ UNCOMMITTED``, ``READ COMMITTED``, ``REPEATABLE READ``, ``SERIALIZABLE``. It will **not** include the ``AUTOCOMMIT`` isolation level setting. Third party dialects may also feature additional isolation level settings. .. note:: This method **will not report** on the ``AUTOCOMMIT`` isolation level, which is a separate :term:`dbapi` setting that's independent of **actual** isolation level. When ``AUTOCOMMIT`` is in use, the database connection still has a "traditional" isolation mode in effect, that is typically one of the four values ``READ UNCOMMITTED``, ``READ COMMITTED``, ``REPEATABLE READ``, ``SERIALIZABLE``. Compare to the :attr:`_engine.Connection.default_isolation_level` accessor which returns the isolation level that is present on the database at initial connection time. .. versionadded:: 0.9.9 .. seealso:: :attr:`_engine.Connection.default_isolation_level` - view default level :paramref:`_sa.create_engine.isolation_level` - set per :class:`_engine.Engine` isolation level :paramref:`.Connection.execution_options.isolation_level` - set per :class:`_engine.Connection` isolation level N)rget_isolation_levelr&ryrzr{s r+r~zConnection.get_isolation_level!sMN D<<33DOOD D D  ( (D$d C C Ds$' AA  Ac.|jjS)aThe 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 :paramref:`.Engine.execution_options.isolation_level` execution options, and is determined by the :class:`_engine.Dialect` when the first connection is created, by performing a SQL query against the database for the current isolation level before any additional commands have been emitted. Calling this accessor does not invoke any new SQL queries. .. versionadded:: 0.9.9 .. seealso:: :meth:`_engine.Connection.get_isolation_level` - view current actual isolation level :paramref:`_sa.create_engine.isolation_level` - set per :class:`_engine.Engine` isolation level :paramref:`.Connection.execution_options.isolation_level` - set per :class:`_engine.Connection` isolation level )rdefault_isolation_levelrKs r+rz"Connection.default_isolation_levelMs:||333r-c|jr(tjd|jdndzd|jrJtjd|jdndzd)Nz;Can't reconnect until invalid %stransaction is rolled back.z savepoint 8s2b)codez\This connection is on an inactive %stransaction. Please rollback() fully before proceeding.8s2a)rtr rwrrWrKs r+_invalid_transactionzConnection._invalid_transactionls   **//;!    &&**=//;!   r-c:|jr|jjS|jrU|jrI|j|j |j j||_|jStjd)N) _connectionThis Connection is closed) rrvr!rtrrrrrr rxrKs r+rvz!Connection._revalidate_connections   %%<<> >   D$4$4  ,))+%)[[%?%? &@&D ")) )%%&ABBr-cP|jduxrt|jddS)Nis_validF)rgetattrrKs r+)_still_open_and_dbapi_connection_is_validz4Connection._still_open_and_dbapi_connection_is_valids.%%T1 g  " "J7  r-c.|jjS)aInfo 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`. )r&r>rKs r+r>zConnection.infos###r-z:meth:`.Connection.connect`c"|jS)aReturns a branched version of this :class:`_engine.Connection`. The :meth:`_engine.Connection.close` method on the returned :class:`_engine.Connection` can be called and this :class:`_engine.Connection` will remain open. This method provides usage symmetry with :meth:`_engine.Engine.connect`, including for usage with context managers. )rUr%r's r+connectzConnection.connects||~r-c |jr|jj|S|jry|jrt j d|j r|jj|d|_y)aInvalidate 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` ) exceptionNr)r invalidatertrrr rxrr)r%rs r+rzConnection.invalidatesr\   %%0090E E     ;;))*EF F  9 9  " " - -i 8!%r-c8|jjy)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). N)rdetachrKs r+rzConnection.detachs4 %%'r-c$|jyr_)beginrKs r+ _autobeginzConnection._autobegin rhr-cD|jr|jr(J|jr|jjS|jry|jt ||_|jS|jrt jdt|S)aBegin a transaction and return a transaction handle. The returned object is an instance of :class:`.Transaction`. This object represents the "scope" of the transaction, which completes when either the :meth:`.Transaction.rollback` or :meth:`.Transaction.commit` method is called. .. tip:: The :meth:`_engine.Connection.begin` method is invoked when using the :meth:`_engine.Engine.begin` context manager method as well. All documentation that refers to behaviors specific to the :meth:`_engine.Connection.begin` method also apply to use of the :meth:`_engine.Engine.begin` method. Legacy use: nested calls to :meth:`.begin` on the same :class:`_engine.Connection` will return new :class:`.Transaction` objects that represent an emulated transaction within the scope of the enclosing transaction, that is:: trans = conn.begin() # outermost transaction trans2 = conn.begin() # "nested" trans2.commit() # does nothing trans.commit() # actually commits Calls to :meth:`.Transaction.commit` only have an effect when invoked via the outermost :class:`.Transaction` object, though the :meth:`.Transaction.rollback` method of any of the :class:`.Transaction` objects will roll back the transaction. .. tip:: The above "nesting" behavior is a legacy behavior specific to :term:`1.x style` use and will be removed in SQLAlchemy 2.0. For notes on :term:`2.0 style` use, see :meth:`_future.Connection.begin`. .. seealso:: :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` NzThis connection has already initialized a SQLAlchemy Transaction() object via begin() or autobegin; can't call begin() here unless rollback() or commit() is called first.) rWrrr rRootTransactionr InvalidRequestErrorMarkerTransactionrKs r+rzConnection.beginsf ??)) ))   %%++- - ??     & / 5D $$ $--')..r-c2|jr|jr(J|jr|jjS|jA|js%t j d|j S|jt|S)aBegin a nested transaction (i.e. SAVEPOINT) and return a transaction handle, assuming an outer transaction is already established. Nested transactions require SAVEPOINT support in the underlying database. Any transaction in the hierarchy may ``commit`` and ``rollback``, however the outermost transaction still controls the overall ``commit`` or ``rollback`` of the transaction of a whole. The legacy form of :meth:`_engine.Connection.begin_nested` method has alternate behaviors based on whether or not the :meth:`_engine.Connection.begin` method was called previously. If :meth:`_engine.Connection.begin` was not called, then this method will behave the same as the :meth:`_engine.Connection.begin` method and return a :class:`.RootTransaction` object that begins and commits a real transaction - **no savepoint is invoked**. If :meth:`_engine.Connection.begin` **has** been called, and a :class:`.RootTransaction` is already established, then this method returns an instance of :class:`.NestedTransaction` which will invoke and manage the scope of a SAVEPOINT. .. tip:: The above mentioned behavior of :meth:`_engine.Connection.begin_nested` is a legacy behavior specific to :term:`1.x style` use. In :term:`2.0 style` use, the :meth:`_future.Connection.begin_nested` method instead autobegins the outer transaction that can be committed using "commit-as-you-go" style; see :meth:`_future.Connection.begin_nested` for migration details. .. versionchanged:: 1.4.13 The behavior of :meth:`_engine.Connection.begin_nested` as returning a :class:`.RootTransaction` if :meth:`_engine.Connection.begin` were not called has been restored as was the case in 1.3.x versions; in previous 1.4.x versions, an outer transaction would be "autobegun" but would not be committed. .. seealso:: :meth:`_engine.Connection.begin` :ref:`session_begin_nested` - ORM support for SAVEPOINT a(Calling Connection.begin_nested() in 2.0 style use will return a NestedTransaction (SAVEPOINT) in all cases, that will not commit the outer transaction. For code that is cross-compatible between 1.x and 2.0 style use, ensure Connection.begin() is called before calling Connection.begin_nested().) rWr begin_nestedrrwarn_deprecated_20rrNestedTransactionrKs r+rzConnection.begin_nested\s` ??)) ))   %%224 4    $??''1zz|#! &&r-c|jr|jj|S|jtjd|$|j j j}t||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` )xidzOCannot start a two phase transaction when a transaction is already in progress.) rbegin_twophaserr rrr create_xidTwoPhaseTransaction)r%rs r+rzConnection.begin_twophasesw(   %%444= =    ())*  ;++%%002C"4--r-cL|jjj|Sr_)rrdo_recover_twophaserKs r+recover_twophasezConnection.recover_twophases{{""66t< >'''r-c|jrJ|jr3|jr|jdn|jdd|_|j s|j j r|jj| |j jj|jd|_y#t$r}|j|ddddYd}~+d}~wwxYw#d|_wxYw)Nz?BEGIN (implicit; DBAPI should not BEGIN due to autocommit mode)zBEGIN (implicit)TF)rrrrDr rrrrrdo_beginr&ryrzr% transactionr|s r+ _begin_implzConnection._begin_impls%%%% ::,,.' 12   t{{66 MM   % $ KK   ( ( 9$DO D  ( (D$d C C D$DOs*/C C2C-(C5-C22C55 C>c|jrJ|js|jjr|jj ||j rp|j r3|jr|jdn|jd |jjj|jyy#t$r}|j|ddddYd}~yd}~wwxYw)NzVROLLBACK using DBAPI connection.rollback(), DBAPI should ignore due to autocommit modeROLLBACK)rrrrrollbackrrrrDr do_rollbackr&ryrzr{s r+_rollback_implzConnection._rollback_impls%%%%   t{{66 MM " "4 (  9 9zz002NNE NN:. H ##//@ :! H,,QdD$GG Hs/C C1C,,C1c|jrJ|r%|jstjd|js|j jr|j j||jr3|jr|jdn|jd |j jj|jy#t$r}|j|ddddYd}~yd}~wwxYw)NzThe current statement is being autocommitted using implicit autocommit, which will be removed in SQLAlchemy 2.0. Use the .begin() method of Engine or Connection in order to use an explicit transaction for DML and DDL statements.zRCOMMIT using DBAPI connection.commit(), DBAPI should ignore due to autocommit modeCOMMIT)rrrrrrrcommitrrDr do_commitr&ryrz)r% autocommitr|s r+ _commit_implzConnection._commit_impl*s%%%% d;;=  # #J    t{{66 MM  & ::,,.A x( D KK   ) )$// : D  ( (D$d C C Ds3/C## D ,DD cP|jrJ|js|jjr|jj |||$|xj dz c_d|j z}|j r(|jjj|||Sy)Nrzsa_savepoint_%s) rrrr savepointrrr do_savepointr%rQs r+_savepoint_implzConnection._savepoint_implJs%%%%   t{{66 MM # #D$ / <  A % $t';';;D  9 9 KK   , ,T4 8K :r-c|jrJ|js|jjr|jj ||d|j r'|jj j||yyr_)rrrrrollback_savepointrrdo_rollback_to_savepointrs r+_rollback_to_savepoint_implz&Connection._rollback_to_savepoint_implWsd%%%%   t{{66 MM , ,T4 >  9 9 KK   8 8t D :r-c|jrJ|js|jjr|jj ||d|j r'|jj j||yyr_)rrrrrelease_savepointrrdo_release_savepointrs r+_release_savepoint_implz"Connection._release_savepoint_impl`sd%%%%   t{{66 MM + +D$ =  9 9 KK   4 4T4 @ :r-c|jrJ|jr|jd|js|jjr&|j j ||j|jr@d|_ |jjj||jd|_ yy#t$r}|j|ddddYd}~,d}~wwxYw#d|_ wxYw)NzBEGIN TWOPHASE (implicit)TF)rrrDrrrrrrr rdo_begin_twophaseryrzrs r+_begin_twophase_implzConnection._begin_twophase_implis%%%% :: NN6 7   t{{66 MM ( ({ ?  9 9"DO ( ##55dKOOL#( :! H,,QdD$GG H#(s*0C C) C$C,$C))C,, C5c|jrJ|js|jjr|jj |||j rDt |jtsJ |jjj||yy#t$r}|j|ddddYd}~yd}~wwxYwr_) rrrrprepare_twophaser isinstancerrrdo_prepare_twophaseryrz)r%rr|s r+_prepare_twophase_implz!Connection._prepare_twophase_implzs%%%%   t{{66 MM * *4 5  9 9d//1DE EE H ##77cB :! H,,QdD$GG Hs6&B C'CCc|jrJ|js|jjr|jj ||||j rEt |jtsJ |jjj|||yy#t$r}|j|ddddYd}~yd}~wwxYwr_) rrrrrollback_twophaserrrrrrryrzr%r is_preparedr|s r+_rollback_twophase_implz"Connection._rollback_twophase_impls%%%%   t{{66 MM + +D#{ C  9 9d//1DE EE H ##88#{ : ! H,,QdD$GG H7'B C)CCc|jrJ|js|jjr|jj ||||j rEt |jtsJ |jjj|||yy#t$r}|j|ddddYd}~yd}~wwxYwr_) rrrrcommit_twophaserrrrrrryrzrs r+_commit_twophase_implz Connection._commit_twophase_impls%%%%   t{{66 MM ) )$[ A  9 9d//1DE EE H ##66tS+N :! H,,QdD$GG Hrc|jr|jj|js|jyyr_)r _autorollbackrrrKs r+rzConnection._autorollbacks:       , , .""$    !%r-c.tjdy)Na The connection.execute() method in SQLAlchemy 2.0 will accept parameters as a single dictionary or a single sequence of dictionaries only. Parameters passed as keyword arguments, tuples or positionally oriented dictionaries and/or tuples will no longer be accepted.)rrrKs r+_warn_for_legacy_exec_formatz'Connection._warn_for_legacy_exec_formats  * r-cl|jr2|jrJtjdd|_d|_y|j r|j jd}nd}|j8|j}|r|jdn|jd|_d|_y)afClose this :class:`_engine.Connection`. This results in a release of the underlying database resources, that is, the DBAPI connection referenced internally. The DBAPI connection is typically restored back to the connection-holding :class:`_pool.Pool` referenced by the :class:`_engine.Engine` that produced this :class:`_engine.Connection`. Any transactional state present on the DBAPI connection is also unconditionally released via the DBAPI connection's ``rollback()`` method, regardless of any :class:`.Transaction` object that may be outstanding with regards to this :class:`_engine.Connection`. After :meth:`_engine.Connection.close` is called, the :class:`_engine.Connection` is permanently in a closed state, and will allow no further operations. zThe .close() method on a so-called 'branched' connection is deprecated as of 1.4, as are 'branched' connections overall, and will be removed in a future release. If this is a default-handling function, don't close the connection.NFT)transaction_reset) rrWrrrr!rrb_close_special)r% skip_resetconns r+rbzConnection.closes(    &&  # #I  &*D "#(D        # # %JJ  ! ! -))D##d#; &*D "$r-cJ|j|g|i|jS)zExecutes and returns the first column of the first row. The underlying result/cursor is closed after execution. executescalarr%object_ multiparamsparamss r+rzConnection.scalars(t||G`_ for details on paramstyle. To execute a textual SQL statement which uses bound parameters in a DBAPI-agnostic way, use the :func:`_expression.text` construct. .. deprecated:: 2.0 use of tuple or scalar positional parameters is deprecated. All params should be dicts or sequences of dicts. Use :meth:`.exec_driver_sql` to execute a plain string with tuple or scalar positional parameters. zPassing a string to Connection.execute() is deprecated and will be removed in version 2.0. Use the text() construct, or the Connection.exec_driver_sql() method to invoke a driver-level SQL string.Ffuturereplace_contextN) rr string_typesr_exec_driver_sql_EMPTY_EXECUTION_OPTS_execute_on_connectionAttributeErrorraise_r ObjectNotExecutableError)r% statementrrmetherrs r+rzConnection.executesV i!2!2 3  # #+ ((% )  J33D k63HI I   KK,,Y7   s A&& B#/*BB#cF|j|j|||S)z%Execute a sql.FunctionElement object.)_execute_clauseelementselect)r%funcrrrms r+_execute_functionzConnection._execute_functionks'** KKM;0A  r-c|jj|}t|||}|js|jjr|j |||\}}}} |j } | |j} |j} | jj| || |}  j!d|d} |j"r|j%|js|jjr |j&j)|||| | S#tjtjf$rt$r} |j| ddddYd} ~ d} ~ wwxYw)z&Execute a schema.ColumnDefault object.N)r merge_withrrr_invoke_before_exec_eventrrvrexecution_ctx_cls _init_defaultr rwrxryrz _exec_defaultrrbr after_execute)r%defaultrrrmdistilled_parametersdistilled_paramsevent_multiparams event_paramsrrctxr|rets r+_execute_defaultzConnection._execute_defaultrsl!33>>   /t[&I   t{{66 ..-/@   ! D))D|224llG++99t%6Cgt4  ( ( JJL   t{{66 MM ' '!!   '((#*A*AB   D  ( (D$d C C Ds$AD,E* E%%E*cP|jj|j|}t|||}|js|jjr|j |||\}}}}|jj|} | j dd} |j} |j| | } |j| | jj| d|| } |js|jjr |jj|||| | S)zExecute a schema.DDL object.rIN)rrI)rrrrrrrJrcompile_execute_contextr _init_ddlrr)r%ddlrrrmr r!r"r# exec_optsrIrcompiledr%s r+ _execute_ddlzConnection._execute_ddls6 22==  # #%6  /t[&I   t{{66 ..)+<   ! ++667HI (}}-CTJ,,;;2F ##   % % / /         t{{66 MM ' '!!   r-ct|dk(rg|d}}n|i}}|jjD]}||||||\}}}|r"t|}|rt j d|r|g}ng}||||fS)NrrzLEvent handler can't return non-empty multiparams and params at the same time)lenrbefore_executelistr r)r%elemr!rmr"r#fns r+rz$Connection._invoke_before_exec_events  A %.02B12E| .>| --.. B46!! 5 1D#\  #$56 --2 ,~ ! %'8,FFr-c |jj|j|}t|||}|jxs|jj}|r|j |||\}}}}|rt |d} t|dkD} ng} d} |j} |jdd} |jd|jj} |j| | | | | |jjtjz\}}}|j| | j j"|||||||| }|r |j$j'|||||S) z#Execute a sql.ClauseElement object.rrFrINcompiled_cache)rr6 column_keysfor_executemanyrIlinting) cache_hit)rrrrrrsortedr0rrJ_compiled_cache_compile_w_cachecompiler_lintingr WARN_LINTINGr)r_init_compiledrr)r%r3rrrmr! has_eventsr"r#keysr8rrIr6 compiled_sqlextracted_paramsr:r%s r+rz!Connection._execute_clauseelements !33>>  # #%6 +4fE%%@)@)@  ..&(9   ! *1-.D!"23a7OD#O,,044 "D +.. dkk99 594I4I)+!5LL11H4I4II 5J5 1 & ##   % % 4 4       $    MM ' '!!   r-c |jj|j|}t|||}|js|j jr|j |||\}}}}|j} |j| | jj|||||dd } |js|j jr |jj|||| | S)ziExecute a sql.Compiled object. TODO: why do we have this? likely deprecate or remove N) rmrrrrrrrr)rr@rr) r%r-rrrmr r!r"r#rr%s r+_execute_compiledzConnection._execute_compiled@s%66AA  # #%6  /t[&I   t{{66 ...0A   ! ,,##   % % 4 4          t{{66 MM ' '!!   r-c |jj|}t|||}|s:|js|jjr|j |||\}}}} |j } |j| | jj|||||} |sB|js|jjr |jj|| || | Sr_) rrrrrrrr)r_init_statementrr) r%rrrrmrr r!r"r#rr%s r+r zConnection._exec_driver_sqlts!33>>   /t[&I4;;#:#: 2235F $% ,,##   % % 5 5     4;;#:#: ++% %  r-ct|\}} |j}|||||S#t$r4}tjt j ||Yd}~yd}~wwxYw)Nr)rr r rrr r)r%r parametersrm args_10stylekwargs_10stylerrs r+ _execute_20zConnection._execute_20sk (:*'E$ n O33D lND]}||| ||| | j6\}}|j@r|jC|| jE}|j:jFs4|jCd|tIjJ|d| j6n|jCd |d d } | j6rl|jLj8r4|jLj<jND]}|| ||| sd}n|s|jLjO| ||| n|su| jPri|jLj8r3|jLj<jRD]}|| || sd}n|s|jLjS| || nj|jLj8r4|jLj<jTD]}|| ||| sd}n|s|jLjU| ||| |j8s|j:j8r*|j<jW|| ||| | j6| jY| j[}|j&sw|j\}|j^s |rd|_0|j| jbr|jed |r*| j^r|j&rJ|jg|S#t j t jf$rt$r3} |j| tj||ddYd} ~ d} ~ wwxYw#t$r } |j| ||| | Yd} ~ Sd} ~ wwxYw) zdCreate an :class:`.ExecutionContext` and execute, returning a :class:`_engine.CursorResult`. yield_perNT)stream_resultsmax_row_bufferrz[%s] %r )batchesismultir1z5] [SQL parameters hidden due to hide_parameters=True]F)r)4rrJrjrrvr rwrxryrzr text_typerrrr_trans_context_managerr _trans_ctx_checkrWrpre_execuse_setinputsizes_set_input_sizescursorrrJ executemanyrrrbefore_cursor_executerrD_get_cache_statshide_parameterssql_util _repr_paramsrdo_executemany no_parametersdo_execute_no_params do_executeafter_cursor_execute post_exec_setup_result_proxyr _soft_closed_autoclose_connectionshould_autocommitrrb)r%r constructorrrJrmargsrBbranchedyprcontextr|r]r4stats evt_handledresultrs r+r)zConnection._execute_contexts   %%D "&&{D9B$5$;$;'+rB%! ))D|224!t%69=ACG   %%//((00::  % % '  ( ( 1 1$ 7 ??t008 OO   $ $  $ $ & NN      &  ""#AJ   t{{66mm99 (*'' )% :  :: NN9 %,,.E;;..))"B8K8K  I ""<<++"ll33BB"fiWE*.K!"#LL// :w G$9$9<<++"ll33HH"fi9*.K!"#LL55 7<<++"ll33>>"fiWE*.K!"#LL++ :w4;;#:#: 22''     002F??+3+L+L(**/G37F0 %%-11%%%6 ,0D0D#..NN$ a((#*A*AB     ( (4>>),j$   R   ( (9j&'    sF-R"AT)A8T"A)T DT",T(S<<T T- T((T-c |js|jjr+|jjD]}||||||d\}}|jr#|j ||j d| |j jsdn|j jjD]}|||||sn|j j|||||js|jjr!|jj|||||dyy#t$r}|j|||||Yd}~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 terminates at _execute_context(). Fz [raw sql] %rr2N) rrrr_rrDrrgryrzrh)r%r]rrJrrr4r|s r+_cursor_executezConnection._cursor_executesC   t{{66mm99 (*&)Z%)% :  :: NN9 % NN>: 6 ||//\\**55 P fiW=  P '' :wO   t{{66 MM . .fiWe  7    ( (9j&'   s>AD*!D** E3E  Ec |jy#t$r4|jjjj ddYywxYw)z\Close the given cursor, catching exceptions and turning into log warnings. zError closing cursorT)exc_infoN)rb Exceptionrpoolr=error)r%r]s r+_safe_close_cursorzConnection._safe_close_cursorsG   LLN  KK   # # ) )& *  s:AAc  tj}tj|}|jst ||j jjxrD|j xr5|j j||js |jnd|xs|xr |j |_| }|jrtjtj j#||||j jj|j$j&|j | |j(nd|d|d|_ t ||j jjxs|duxr |duxr| } | r|tj j#||||j jj|j$j&|j|j | |j(nd} nd} d} |j*s|j$j*r|j,j/ddst1|| |j$||||||j| } |j2j4D]} | | }| |x| _} |j| jk7r$| j|_| r| j| _| j<}| r|r|j?||jsB|r|jA|tjBd5|jEddd| rtj| |d|n;| rtj| |d|ntj|d |d |` |jrS|`|jsE|j}|r&|j$jFjI|||jK||jLr|jNrJ|jQyy#t8$r}|} Yd}~d}~wwxYw#1swY xYw#|` |jrS|`|jsE|j}|r&|j$jFjI|||jK||jLr|jNrJ|jQwwxYw) N)rarrVr with_tracebackfrom_T)raconnection_invalidatedrrVskip_user_error_eventsF) warn_onlyrr))sysryris_exit_exception_is_disconnectrrdbapiErrorrr is_disconnectrtr_reentrant_errorrr DBAPIErrorinstancerrar^rrrJExceptionContextImplr handle_errorchained_exceptionrzrinvalidate_pool_on_disconnecthandle_dbapi_exceptionr} safe_reraiserr{ _invalidaterrrWrb)r%r|rrJr]rrryrr should_wrapsqlalchemy_exceptionnewraiser$r4per_fn_raiseddbapi_conn_wrappers r+rzz"Connection._handle_dbapi_exceptions<<> 2215""1dll00667 OLL..262B2BD**#9$7DKK  ->(=%  KK''LL&&,,$(KK$?$? LL*$//(  ({ !%c %Q (:(:(@(@A%*tO*))  '*~~'>'>LL&&,,$(KK$?$?+/+>+> LL*$//(? ($(,$H  DKK$;$;--11(%+(KK''1 --44 B "$C!-?EEC1H &&#*;*;;*-*;*;D'+---C55.w..q1&&++F3&&6)&&() HXa[J (!A HQK D%""''')-)?)?&4 ((445GKOOA&,,??** -[%#*0))%""''')-)?)?&4 ((445GKOOA&,,??** -sRD--at<  GMM$7$78 #&>>#:#: ## & 6 6'4 $;$ $(    &$ Coo22   WF);AA- $ 9J9J(J%%&$;!  KK!A F  KK$Xa[  KK HQK @#!&Hs E E5(E00E5c J||j|fi|j|y)zrun 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. N)rtraverse_single)r%visitorcallableelementkwargss r+_run_ddl_visitorzConnection._run_ddl_visitors"  d5f5EEgNr-1.4zThe :meth:`_engine.Connection.transaction` method is deprecated and will be removed in a future release. Use the :meth:`_engine.Engine.begin` context manager instead.cd|d<|j} |j|g|i|}|j|S#tj5|j dddYy#1swYYyxYwxYw)atExecute the given function within a transaction boundary. The function is passed this :class:`_engine.Connection` as the first argument, followed by the given \*args and \**kwargs, e.g.:: def do_something(conn, x, y): conn.execute(text("some statement"), {'x':x, 'y':y}) conn.transaction(do_something, 5, 10) The operations inside the function are all invoked within the context of a single :class:`.Transaction`. Upon success, the transaction is committed. If an exception is raised, the transaction is rolled back before propagating the exception. .. note:: The :meth:`.transaction` method is superseded by the usage of the Python ``with:`` statement, which can be used with :meth:`_engine.Connection.begin`:: with conn.begin(): conn.execute(text("some statement"), {'x':5, 'y':10}) As well as with :meth:`_engine.Engine.begin`:: with engine.begin() as conn: conn.execute(text("some statement"), {'x':5, 'y':10}) .. seealso:: :meth:`_engine.Engine.begin` - engine-level transactional context :meth:`_engine.Engine.transaction` - engine-level version of :meth:`_engine.Connection.transaction` T_sa_skip_warningN)r run_callablerrrr)r% callable_rortransr%s r+rzConnection.transactions{b&*!"  !#$##I???C LLNJ !""$ !  ! ! !s''?A=A0&A=0A: 5A=:A=zThe :meth:`_engine.Connection.run_callable` method is deprecated and will be removed in a future release. Invoke the callable function directly, passing the Connection.c||g|i|S)aGiven a callable object or function, execute it, passing a :class:`_engine.Connection` as the first argument. The given \*args and \**kwargs are passed subsequent to the :class:`_engine.Connection` argument. This function, along with :meth:`_engine.Engine.run_callable`, allows a function to be run with a :class:`_engine.Connection` or :class:`_engine.Engine` object without the need to know which one is being dealt with. r2)r%rrors r+rzConnection.run_callables(////r-)NFNNNNTFr_NN)U__name__ __module__ __qualname____doc__rW_sqla_logger_namespacerXr,rmemoized_propertyr7rDrGpropertyrLrRrUr]r`rgrmrorrrtr&r~rrrvrr> deprecated_20rrrrrrrrrrrrrrrrrrrrrrrrrrrrbrrrrr r&r.rrrFr rMrOr)rwr}rrrz classmethodrr deprecatedrrr2r-r+rr s8J;" 5In  5 6II( :BH 'KKBB"**2*DX44<2 C   $ $T56 7 9&v(8K/ZC'J.@=MKM    ! ($0H(D@ EA(" H H H"  5%nFG"cJJ 0 6p,\G@FZ0 2h*^/ O"=A@ Dsj&P NHT:A:AxOT__  #2!2!hT__  , 0 0r-rceZdZdZdZy)rz3Implement the :class:`.ExceptionContext` interface.c ||_||_||_||_||_||_||_| |_| |_yr_) rr&roriginal_exceptionexecution_contextrrJrr) r%rrrr&r]rrJrrrrs r+r,zExceptionContextImpl.__init__ sH $$8!"+!("$*-J*r-N)rrrrr,r2r-r+rr s =Kr-rceZdZdZdZdZdZdZedZ dZ dZ d Z ed Z d Zd Zd ZdZdZdZdZy) TransactionatRepresent a database transaction in progress. The :class:`.Transaction` object is procured by calling the :meth:`_engine.Connection.begin` method of :class:`_engine.Connection`:: from sqlalchemy import create_engine engine = create_engine("postgresql://scott:tiger@localhost/test") connection = engine.connect() trans = connection.begin() 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 r2Fctr_NotImplementedErrorr%r&s r+r,zTransaction.__init__E !##r-ct)ado whatever steps are necessary to set this transaction as "deactive", however leave this transaction object in place as far as the connection's state. for a "real" transaction this should roll back the transaction and ensure this transaction is no longer a reset agent. this is used for nesting of marker transactions where the marker can set the "real" transaction as rolled back, however it stays in place. for 2.0 we hope to remove this nesting feature. rrKs r+_do_deactivatezTransaction._do_deactivateH s "##r-ct)zTrue if this transaction is totally deactivated from the connection and therefore can no longer affect its state. rrKs r+_deactivated_from_connectionz(Transaction._deactivated_from_connectionY s "##r-ctr_rrKs r+ _do_closezTransaction._do_closea rr-ctr_rrKs r+ _do_rollbackzTransaction._do_rollbackd rr-ctr_rrKs r+ _do_commitzTransaction._do_commitg rr-cL|jxr|jj Sr_)rr&rtrKs r+rzTransaction.is_validj s~~Adoo&A&A"AAr-ch |j|jrJy#|jrJwxYw)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)rrrKs r+rbzTransaction.closen s0 & NN ~~ %%~t~~ %%~!1ch |j|jrJy#|jrJwxYw)aRoll 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)rrrKs r+rzTransaction.rollback~ s2" &    ~~ %%~t~~ %%~rch |j|jrJy#|jrJwxYw)aCommit 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 phase transactions may be used. N)rrrKs r+rzTransaction.commit s0  & OO ~~ %%~t~~ %%~rc|jSr_)r&rKs r+ _get_subjectzTransaction._get_subject s r-c|jSr_rrKs r+_transaction_is_activez"Transaction._transaction_is_active s ~~r-c|j Sr_)rrKs r+_transaction_is_closedz"Transaction._transaction_is_closed s4444r-cyNTr2rKs r+_rollback_can_be_calledz#Transaction._rollback_can_be_called s r-N)rrrr __slots___is_rootr,rrrrrrrrbrrrrrrr2r-r+rr sz"HIH$$"$$$$$BB& &,&*5r-rcReZdZdZdZdZedZedZdZ dZ dZ d Z y ) rzA 'marker' transaction that is used for nested begin() calls. .. deprecated:: 1.4 future connection for 2.0 won't support this pattern. )r& _is_activerc|jJ|jjstjd|jrJt j d||_|jrtj||j|j|_d|_ y|j|_d|_ y)NzWthe current transaction on this connection is inactive. Please issue a rollback first.zCalling .begin() when a transaction is already begun, creating a 'sub' transaction, is deprecated and will be removed in 2.0. See the documentation section 'Migrating from the nesting pattern' for background on how to migrate from this pattern.T) rrr rrWrrr&rXr rYrrrs r+r,zMarkerTransaction.__init__ s&&222&&00))1  ((((  , %  , , 1 1* =  ) ) 5 * > >D !+ 7 7D r-c|j Sr_rrKs r+rz.MarkerTransaction._deactivated_from_connection s>>!!r-cJ|jxr|jjSr_)rrrrKs r+rzMarkerTransaction.is_active s>4#4#4#>#>>r-cd|_yNF)rrKs r+ _deactivatezMarkerTransaction._deactivate s r-c$|jyr_rrKs r+rzMarkerTransaction._do_close s r-c|jr, |jj|jyy#|jwxYwr_)rrrrrKs r+rzMarkerTransaction._do_rollback sA ?? #!!002  "   "s :A c$|jyr_rrKs r+rzMarkerTransaction._do_commit  r-N) rrrrrr,rrrrrrrr2r-r+rr sO =I8""?? #r-rcfeZdZdZdZdZdZdZedZ dZ dZ d Z d Z dd Zd Zd ZdZy)raRepresent the "root" transaction on a :class:`_engine.Connection`. This corresponds to the current "BEGIN/COMMIT/ROLLBACK" that's occurring for the :class:`_engine.Connection`. The :class:`_engine.RootTransaction` is created by calling upon the :meth:`_engine.Connection.begin` method, and remains associated with the :class:`_engine.Connection` throughout its active span. The current :class:`_engine.RootTransaction` in use is accessible via the :attr:`_engine.Connection.get_transaction` method of :class:`_engine.Connection`. In :term:`2.0 style` use, the :class:`_future.Connection` also employs "autobegin" behavior that will create a new :class:`_engine.RootTransaction` whenever a connection in a non-transactional state is used to emit commands on the DBAPI connection. The scope of the :class:`_engine.RootTransaction` in 2.0 style use can be controlled using the :meth:`_future.Connection.commit` and :meth:`_future.Connection.rollback` methods. T)r&rc|jJ|jrtj|||_|j ||_d|_yr)rrXr rYr&_connection_begin_implrrs r+r,zRootTransaction.__init__ sM&&...  , , 1 1* =$ ##%"& r-c|jr"|jj|usJd|_y|jj|urtjdyy)NFz0transaction already deassociated from connection)rr&rrwarnrKs r+_deactivate_from_connectionz+RootTransaction._deactivate_from_connection sL >>??//47 77"DN __ ) ) 5 IIH I6r-c2|jj|uSr_)r&rrKs r+rz,RootTransaction._deactivated_from_connection& s++477r-c|jj|usJ|jr|j|jjr$|jjj |j yr_)r&rr_connection_rollback_implr_cancelrrKs r+rzRootTransaction._do_deactivate* s`++t333 >>  * * , ?? . . OO / / 7 7 9 ((*r-c:|jj|yr_)r&rrKs r+rz&RootTransaction._connection_begin_impl? s ##D)r-c8|jjyr_)r&rrKs r+rz)RootTransaction._connection_rollback_implB s &&(r-c8|jjyr_)r&rrKs r+_connection_commit_implz'RootTransaction._connection_commit_implE s $$&r-c, |jr|j|jjr$|jjj |js|r|j |jj |urd|j_ |jrJ|jj |usJy#|js|r|j |jj |urd|j_wwxYwr_)rrr&rrrr)r%try_deactivates r+ _close_implzRootTransaction._close_implH s 4~~..02233;;=~~002++t3/3,>>!!++4777 ~~002++t3/3,4s AC A Dc$|jyr_rrKs r+rzRootTransaction._do_closeX rr-c(|jdy)NT)rrrKs r+rzRootTransaction._do_rollback[ s -r-c|jr|jj|usJ |j|jjr$|jjj |j d|j_nH|jj|ur|jjntjd|jrJ|jj|usJy#|jjr$|jjj |j wxYw)NThis transaction is inactive) rr&rrrrrrr rrKs r+rzRootTransaction._do_commit^ s >>??//47 77 3,,. ??66OO77??A002 ,0DOO (++t3446--.LMM>>!!++4777!??66OO77??A002s DA ENr)rrrrrrr,rrrrrrrrrrrr2r-r+rr sZ*H+IJ88+**)'8 .8r-rcVeZdZdZdZdZd dZedZdZ dZ dZ d Z d Z d Zy )raRepresent a 'nested', or SAVEPOINT transaction. The :class:`.NestedTransaction` object is created by calling the :meth:`_engine.Connection.begin_nested` method of :class:`_engine.Connection`. When using :class:`.NestedTransaction`, the semantics of "begin" / "commit" / "rollback" are as follows: * the "begin" operation corresponds to the "BEGIN SAVEPOINT" command, where the savepoint is given an explicit name that is part of the state of this object. * The :meth:`.NestedTransaction.commit` method corresponds to a "RELEASE SAVEPOINT" operation, using the savepoint identifier associated with this :class:`.NestedTransaction`. * The :meth:`.NestedTransaction.rollback` method corresponds to a "ROLLBACK TO SAVEPOINT" operation, using the savepoint identifier associated with this :class:`.NestedTransaction`. The rationale for mimicking the semantics of an outer transaction in terms of savepoints so that code may deal with a "savepoint" transaction and an "outer" transaction in an agnostic way. .. seealso:: :ref:`session_begin_nested` - ORM version of the SAVEPOINT API. )r&r _savepoint_previous_nestedc|jJ|jrtj|||_|jj |_d|_|j|_ ||_yr) rrXr rYr&rrrrrrs r+r,zNestedTransaction.__init__ sc&&222  , , 1 1* =$//99; * > >)- &r-c|jj|ur|j|j_y|rtjdyy)Nz7nested transaction already deassociated from connection)r&rrrr)r%rs r+rz-NestedTransaction._deactivate_from_connection s= ?? . .$ 6262G2GDOO /  III r-c2|jj|uSr_)r&rrKs r+rz.NestedTransaction._deactivated_from_connection s22$>>r-cd|_|j|jr|jjyyr)rrrrrKs r+rzNestedTransaction._cancel s7 ((*   ! ! ) ) + !r-cx |jrE|jjjr%|jj|jd|_|r|j | |jrJ|r|jj |usJyy#d|_|r|j |wwxYw)NF)r)rr&rrrrr)r%deactivate_from_connectionwarn_already_deactives r+rzNestedTransaction._close_impl s M~~$//">">"H"H;;DOOL"DN)006K0L>>!! %??66dB BB & #DN)006K0L*s ABB9c(|jddyrrrKs r+rz NestedTransaction._do_deactivate s &r-c(|jddy)NTFrrKs r+rzNestedTransaction._do_close s u%r-c(|jddyrrrKs r+rzNestedTransaction._do_rollback s t$r-c>|jr> |jj|jd|_|j y|jj |ur|jj ytjd#d|_wxYw)NFz#This nested transaction is inactive) rr&rrrrrr rrKs r+rzNestedTransaction._do_commit s~ >> '77H "'  , , .22d:446--9"'s %B BNT)rrrrrr,rrrrrrrrrr2r-r+rr{ sL>NI.??, C'&%r-rc>eZdZdZdZfdZdZdZdZdZ xZ S)raRepresent a two-phase transaction. A new :class:`.TwoPhaseTransaction` object may be procured using the :meth:`_engine.Connection.begin_twophase` method. The interface is the same as that of :class:`.Transaction` with the addition of the :meth:`prepare` method. )r&rr _is_preparedcHd|_||_tt||yr)rrsuperrr,)r%r&rrXs r+r,zTwoPhaseTransaction.__init__ s"! !41*=r-c|jstjd|jj |j d|_y)zqPrepare this :class:`.TwoPhaseTransaction`. After a PREPARE, the transaction can be committed. rTN)rr rr&rrrrKs r+preparezTwoPhaseTransaction.prepare s; ~~))*HI I ..txx8 r-c:|jj|yr_)r&rrKs r+rz*TwoPhaseTransaction._connection_begin_impl s ,,T2r-cd|jj|j|jyr_)r&rrrrKs r+rz-TwoPhaseTransaction._connection_rollback_impl s  //$:K:KLr-cd|jj|j|jyr_)r&rrrrKs r+rz+TwoPhaseTransaction._connection_commit_impl s  --dhh8I8IJr-) rrrrrr,rrrr __classcell__)rXs@r+rr s+CI> !3MKr-rceZdZdZeZdZeZdZ dZ dZ d,dZ dZ edZdZd Zd Zd Zed Zed Zej.ZdZd-dZdej8fdZej>d.dZ Gdde!Z"d/dZ#ejHdddZ%ejHdddZ&dZ'ejPdddZ)ejPd d!d"Z*ddefd#Z+efd$Z,d/d%Z-ejHdd&d0d'Z.ejHdd(d.d)Z/d*Z0d.d+Z1y)1Enginea9 Connects a :class:`~sqlalchemy.pool.Pool` and :class:`~sqlalchemy.engine.interfaces.Dialect` together to provide a source of database connectivity and behavior. This is the **SQLAlchemy 1.x version** of :class:`_engine.Engine`. For the :term:`2.0 style` version, which includes some API differences, see :class:`_future.Engine`. An :class:`_engine.Engine` object is instantiated publicly using the :func:`~sqlalchemy.create_engine` function. .. seealso:: :doc:`/core/engines` :ref:`connections_toplevel` Fzsqlalchemy.engine.EngineNc ||_||_||_|r||_||_||_|dk7r't j||j|_ nd|_ tj|||r|jdi|yy)Nr) size_alertechoflagr2) r{urlr logging_nameechorarLRUCache_lru_size_alertr<r instance_loggerupdate_execution_options) r%r{rr r!r"query_cache_sizermras r+r,zEngine.__init__, s   ,D  . q #'== T-A-A$D $(D  D40  )D ) ) >,= > r-c~|jr1|jjdt||jyy)NziCompiled cache size pruning from %d items to %d. Increase cache size to reduce the frequency of pruning.)r"r=r>r0capacity)r%caches r+r$zEngine._lru_size_alertH s6  KK  JE    !r-c|Sr_r2rKs r+rz Engine.engineQ s r-cR|jr|jjyy)aClear 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 :paramref:`.Connection.execution_options.query_cache` parameter. .. versionadded:: 1.4 N)r<clearrKs r+clear_compiled_cachezEngine.clear_compiled_cacheU s$     & & ( r-c |jj||_|jj|||jj||y)aUpdate 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)rrjrset_engine_execution_optionsrr%rls r+r&zEngine.update_execution_optionsc sE"#'"9"9"?"?"D 224= 11$J  II   II&&(  %%d+r-r2ct|j5}|j|||cdddS#1swYyxYwr_)rr&)r%rrrrs r+r&zEngine._execute_default s:\\^ Gt((+vF G G Gs.7c#lK||j5}|dddy|y#1swYyxYwwr_)r)r%r&rs r+_optional_conn_ctx_managerz!Engine._optional_conn_ctx_manager s=   4      s4(414ceZdZdZdZdZy)Engine._trans_ctxc.||_||_||_yr_)rrr')r%rrr's r+r,zEngine._trans_ctx.__init__ sDI*D %6D "r-cN|jj|jSr_)rr`rrKs r+r`zEngine._trans_ctx.__enter__ s    & & (99 r-c |jj||||js|jj yy#|js|jj wwxYwr_)rrgr'rrbrcs r+rgzEngine._trans_ctx.__exit__$ sX &  ))% B--IIOO%.t--IIOO%.s A)A0N)rrrr,r`rgr2r-r+ _trans_ctxrC s 7   &r-rGcF|jjr|j}n|j|} |j}tj||S#t j 5|j dddn #1swYnxYwYUxYw)aXReturn 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. Legacy use only: the ``close_with_result`` flag is normally ``False``, and indicates that the :class:`_engine.Connection` will be closed when the operation is complete. When set to ``True``, it indicates the :class:`_engine.Connection` is in "single use" mode, where the :class:`_engine.CursorResult` returned by the first call to :meth:`_engine.Connection.execute` will close the :class:`_engine.Connection` when that :class:`_engine.CursorResult` has exhausted all result rows. .. seealso:: :meth:`_engine.Engine.connect` - procure a :class:`_engine.Connection` from an :class:`_engine.Engine`. :meth:`_engine.Connection.begin` - start a :class:`.Transaction` for a particular :class:`_engine.Connection`. r'N) rTrWrrrrrbrrG)r%r'rrs r+rz Engine.begin+ sF    * *<<>D<<2C<DD JJLE  u.?@@ ""$     s#A""B 8B B B B rzThe :meth:`_engine.Engine.transaction` method is deprecated and will be removed in a future release. Use the :meth:`_engine.Engine.begin` context manager instead.cd|d<|j5}|j|g|i|cdddS#1swYyxYw)aExecute the given function within a transaction boundary. The function is passed a :class:`_engine.Connection` newly procured from :meth:`_engine.Engine.connect` as the first argument, followed by the given \*args and \**kwargs. e.g.:: def do_something(conn, x, y): conn.execute(text("some statement"), {'x':x, 'y':y}) engine.transaction(do_something, 5, 10) The operations inside the function are all invoked within the context of a single :class:`.Transaction`. Upon success, the transaction is committed. If an exception is raised, the transaction is rolled back before propagating the exception. .. note:: The :meth:`.transaction` method is superseded by the usage of the Python ``with:`` statement, which can be used with :meth:`_engine.Engine.begin`:: with engine.begin() as conn: conn.execute(text("some statement"), {'x':5, 'y':10}) .. seealso:: :meth:`_engine.Engine.begin` - engine-level transactional context :meth:`_engine.Connection.transaction` - connection-level version of :meth:`_engine.Engine.transaction` TrN)rrr%rrorrs r+rzEngine.transactionY sN^&*!" \\^ @t#4##I??? @ @ @6?zThe :meth:`_engine.Engine.run_callable` method is deprecated and will be removed in a future release. Use the :meth:`_engine.Engine.begin` context manager instead.cd|d<|j5}|j|g|i|cdddS#1swYyxYw)aGiven a callable object or function, execute it, passing a :class:`_engine.Connection` as the first argument. The given \*args and \**kwargs are passed subsequent to the :class:`_engine.Connection` argument. This function, along with :meth:`_engine.Connection.run_callable`, allows a function to be run with a :class:`_engine.Connection` or :class:`_engine.Engine` object without the need to know which one is being dealt with. TrN)rrrKs r+rzEngine.run_callable sM(&*!" \\^ At$4$$Y@@@ A A ArLc v|j5}|j||fi|dddy#1swYyxYwr_)rr)r%rrrrs r+rzEngine._run_ddl_visitor s= ZZ\ FT !D ! !/7 Ef E F F Fs/8z:meth:`_engine.Engine.execute`zAll statement execution in SQLAlchemy 2.0 is performed by the :meth:`_engine.Connection.execute` method of :class:`_engine.Connection`, or in the ORM by the :meth:`.Session.execute` method of :class:`.Session`.) alternativecR|jd}|j|g|i|S)aExecutes the given construct and returns a :class:`_engine.CursorResult`. The arguments are the same as those used by :meth:`_engine.Connection.execute`. Here, a :class:`_engine.Connection` is acquired using the :meth:`_engine.Engine.connect` method, and the statement executed with that connection. The returned :class:`_engine.CursorResult` is flagged such that when the :class:`_engine.CursorResult` is exhausted and its underlying cursor is closed, the :class:`_engine.Connection` created here will also be closed, which allows its associated DBAPI connection resource to be returned to the connection pool. TrI)rr)r%rrrr&s r+rzEngine.execute s14\\D\9 !z!!)DkDVDDr-z:meth:`_engine.Engine.scalar`a'All statement execution in SQLAlchemy 2.0 is performed by the :meth:`_engine.Connection.execute` method of :class:`_engine.Connection`, or in the ORM by the :meth:`.Session.execute` method of :class:`.Session`; the :meth:`_future.Result.scalar` method can then be used to return a scalar result.cJ|j|g|i|jS)zExecutes and returns the first column of the first row. The underlying result/cursor is closed after execution. r)r%rrrs r+rz Engine.scalar s(t||I> >v>EEGGr-cN|jd}|j||||SNTrI)rr)r%r3rrrmr&s r+rzEngine._execute_clauseelement s1\\D\9 00 +v'8  r-cN|jd}|j||||SrS)rrF)r%r-rrrmr&s r+rFzEngine._execute_compiled s1\\D\9 ++ k6+<  r-c(|j||S)aReturn a new :class:`_engine.Connection` object. The :class:`_engine.Connection` object is a facade that uses a DBAPI connection internally in order to communicate with the database. This connection is procured from the connection-holding :class:`_pool.Pool` referenced by this :class:`_engine.Engine`. When the :meth:`_engine.Connection.close` method of the :class:`_engine.Connection` object is called, the underlying DBAPI connection is then returned to the connection pool, where it may be used again in a subsequent call to :meth:`_engine.Engine.connect`. rI)rTrs r+rzEngine.connect s##D>*V>< = = =s (AA c6|j} |S#|jj$rj}|tj |||nFt j tjdtjdYd}~yYd}~yd}~wwxYw)Nrr r) rrrrrrrrry)r%r4r&rr|s r+_wrap_pool_connectzEngine._wrap_pool_connect( s,, 4K}}"" !??w LLN1%cllnQ6G  sBABBcN|j|jj|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. .. seealso:: :ref:`dbapi_connections` )r_r{r)r%rs r+rzEngine.raw_connection6 s!,&&tyy'8'8+FFr-)NNiNFrr_rr)2rrrrr rrrrTrrWrLr,r$rrr.r&rmrorQr7r echo_propertyr"r:r<r EMPTY_DICTr& contextlibcontextmanagerrAobjectrGrrrrrrrrrrFrrZr\r_rr2r-r+rr s(/K O7J  ?8 )=*J+X '!! ## 3   D*(,V$&dooG &V&",A\T__  )@)@VT__  #AA"FT(EE*T'* H H/  "0  O"T__  9 0 0T__  3== Gr-rcReZdZdZdZdZdZeeeZdZ dZ ee e Z y)OptionEngineMixinFc||_|j|_|j|_|j|_|j|_|j |_|j |_tj||j|jj|j|_ |j|_ |jdi|y)Nrr2) _proxiedr rr!r"r<rar r%rr#rr&)r%proxiedrms r+r,zOptionEngineMixin.__init__R s ;; #00LL &66&66 D4995 ++G,<,<= ")"<"<%%%:(9:r-c.|jjSr_rir{rKs r+ _get_poolzOptionEngineMixin._get_poolm s}}!!!r-c&||j_yr_rl)r%r{s r+ _set_poolzOptionEngineMixin._set_poolp s! r-cj|jjxs|jjddS)NrF)rirrZrJrKs r+_get_has_eventsz!OptionEngineMixin._get_has_eventsu s/}}(( DMM,=,= 5-  r-c"||jd<y)Nr)rZ)r%res r+_set_has_eventsz!OptionEngineMixin._set_has_eventsz s', m$r-N) rrr_sa_propagate_class_eventsr,rmrorr{rqrsrr2r-r+rgrgO s=!&;6"" Iy )D -?Or|s& #(!$&"+**,^#0^#0BGK+K6[&[|= =@~8k~8Bj jZ$K/$KN}G[#..}G@.=.=b $f "r-