JezK
Edit File: base.pyc
� 1��fc @� s� d d l m Z d d l Z d d l Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z e j � Z d e f d � � YZ d e f d � � YZ d e f d � � YZ d e f d � � YZ d e f d � � YZ d e f d � � YZ d e f d � � YZ d e e j f d � � YZ d e f d � � YZ d! e e f d" � � YZ e e _ d S(# i����( t with_statementNi ( t Connectable( t ExceptionContext( t _distill_params( t _distill_params_20( t TransactionalContexti ( t exc( t inspection( t log( t util( t compilert Connectionc B� sD e Z d Z e Z d Z e Z e e e e e e e d � Z e j d � � Z d � Z d � Z e d � � Z d � Z d � Z d � Z d � Z d � Z d � Z d � Z e d � � Z e d � � Z e d � � Z d � Z e d � � Z d � Z d � Z e d � � Z e d � � Z e j! d � e d � � Z" e d � Z# d � Z$ d � Z% d � Z& d � Z' e d � Z( d � Z) e d � Z* e d! � Z+ d" � Z, d# � Z- d$ � Z. d% � Z/ d& � Z0 d' � Z1 d( � Z2 e d) � Z3 e d* � Z4 d+ � Z5 d, � Z6 d- � Z7 d. � Z8 d/ � Z9 d0 � Z: d1 � Z; d2 � Z< d3 � Z= d4 � Z> d5 � Z? d6 � Z@ d7 � ZA eB d8 � ZC d9 � ZD d: � ZE d; � ZF eB d< � ZG d= � ZH e eB d> � ZI e e d? � ZJ d@ � ZK e dA � ZL dB � ZM e ZN e ZO dC � ZP eQ dD � � ZR dE � ZS e jT dF dG � dH � � ZU e jT dF dI � dJ � � ZV RS(K s Provides 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 s sqlalchemy.engine.Connectionc C� sr | | _ | j | _ | | _ | rx | j d k s9 t � | | _ | | _ | j | _ t | _ | | _ | j | _ n� | d k r� | n | j � | _ d | _ | _ d | _ t | _ | | _ | | _ | j j � | _ | d k r| j j | j � | _ n | p | d k o | j | _ | s1t � | j | _ | j sR| j j rn| j j | | d k � n d S( s Construct a new Connection.i N( t enginet dialectt _Connection__branch_fromt Nonet AssertionErrort _dbapi_connectiont _execution_optionst _echot Falset should_close_with_resultt dispatcht _has_eventst raw_connectiont _transactiont _nested_transactiont _Connection__savepoint_seqt _Connection__in_begint _Connection__can_reconnectt _should_log_infot _joint engine_connect( t selfR t connectiont close_with_resultt _branch_fromR t _dispatchR t _allow_revalidate( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt __init__C s6 c � s1 d | j k r) | j d � � f d � Sd Sd S( Nt logging_tokenc � s d � | f S( Ns [%s] %s( ( t msg( t token( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt <lambda>~ t ( R R ( R! ( ( R* sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _message_formatterz s c O� sX | j } | r | | � } n t j r; d t j | d <n | j j j | | | � d S( Ni t stacklevel( R- R t STACKLEVELt STACKLEVEL_OFFSETR t loggert info( R! t messaget argt kwt fmt( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _log_info� s c O� sX | j } | r | | � } n t j r; d t j | d <n | j j j | | | � d S( Ni R. ( R- R R/ R0 R R1 t debug( R! R3 R4 R5 R6 ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _log_debug� s c C� s | j j d d � S( Nt schema_translate_map( R t getR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _schema_translate_map� s c C� sI | j } | j j d d � } | rA | | k rA | j rA | | S| Sd S( st Return the schema name for the given schema item taking into account current schema translate map. R: N( t schemaR R; R t _use_schema_map( R! t objt nameR: ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt schema_for_object� s c C� sL | j j | j | j d | j r* | j n | d | j d | j d | j �S( sz Return 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$ R R R% ( R t _connection_clsR R R R R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _branch� s c C� s< | j r | S| j j | j � } | j j � | _ | Sd S( s@ define connection method chaining behavior for execution_optionsN( t _is_futuret __class__t __new__t __dict__t copy( R! t c( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _generate_for_options� s c C� s | S( N( ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt __enter__� s c C� s | j � d S( N( t close( R! t type_t valuet traceback( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt __exit__� s c K� sc | j � } | j j | � | _ | j s6 | j j rL | j j | | � n | j j | | � | S( s�. 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 <sqlite_isolation_level>` :ref:`PostgreSQL Transaction Isolation <postgresql_isolation_level>` :ref:`MySQL Transaction Isolation <mysql_isolation_level>` :ref:`SQL Server Transaction Isolation <mssql_isolation_level>` :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` ( RJ R t unionR R R t set_connection_execution_optionsR ( R! t optRI ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt execution_options� s � c C� s | j S( s� Get the non-SQL options which will take effect during execution. .. versionadded:: 1.3 .. seealso:: :meth:`_engine.Connection.execution_options` ( R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt get_execution_options� s c C� s | j d k o | j S( s) Return True if this connection is closed.N( R R R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt closed� s c C� s* | j r | j j S| j d k o) | j S( s/ Return True if this connection was invalidated.N( R t invalidatedR R RV ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRW � s c C� sy | j d k rn y | j � SWqu t j t j f k r? � qu t k rj } | j | d d d d � qu Xn | j Sd S( sV The 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 R t _revalidate_connectionR t PendingRollbackErrort ResourceClosedErrort BaseExceptiont _handle_dbapi_exception( R! t e( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR" s c C� sJ y | j j | j � SWn, t k rE } | j | d d d d � n Xd S( s� 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 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( R t get_isolation_levelR" R[ R\ R ( R! R] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR^ ! s 'c C� s | j j S( s 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 :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 ( R t default_isolation_level( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR_ M s c C� s| | j r: t j d | j d k r' d n d d d �� n> | j sJ t � t j d | j d k rh d n d d d �� d S( Ns; Can't reconnect until invalid %stransaction is rolled back.s savepoint R, t codet 8s2bs\ This connection is on an inactive %stransaction. Please rollback() fully before proceeding.t 8s2a( RW R RY R R RD R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _invalid_transactionl s c C� sv | j r | j j � S| j rc | j rc | j d k rD | j � n | j j d | � | _ | j St j d � � d S( Nt _connections This Connection is closed( R RX R RW R R Rc R R R R RZ ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRX � s c C� s" | j d k o! t | j d t � S( Nt is_valid( R R t getattrR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt) _still_open_and_dbapi_connection_is_valid� s c C� s | j j S( s� 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`. ( R" R2 ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR2 � s s :meth:`.Connection.connect`c C� s | j � S( s� Returns 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. ( RC ( R! R# ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt connect� s c C� sm | j r | j j d | � S| j r) d S| j rD t j d � � n | j r` | j j | � n d | _ d S( s� 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` t exceptionNs This Connection is closed( R t invalidateRW RV R RZ Rg R R ( R! Ri ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRj � s . c C� s | j j � d S( s2 Detach 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( R t detach( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRk � s c C� s | j � d S( N( t begin( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _autobegin s c C� s� | j r | j s2 t � n | j r2 | j j � S| j r? d S| j d k rd t | � | _ | j S| j r t j d � � n t | � Sd S( s� Begin 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` Ns� 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.( RD R R Rl R R R t RootTransactionR t InvalidRequestErrort MarkerTransaction( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRl s 3 c C� sx | j r | j s2 t � n | j r2 | j j � S| j d k rn | j sa t j d � | j � S| j � n t | � S( s� Begin 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 s( 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().N( RD R R t begin_nestedR R R t warn_deprecated_20Rl Rm t NestedTransaction( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRq \ s 0 c C� sk | j r | j j d | � S| j d k r= t j d � � n | d k r^ | j j j � } n t | | � S( s' 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` t xidsO Cannot start a two phase transaction when a transaction is already in progress.N( R t begin_twophaseR R R Ro R R t create_xidt TwoPhaseTransaction( R! Rt ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRu � s c C� s | j j j | � S( N( R R t do_recover_twophase( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt recover_twophase� s c C� s | j j j | | d | �d S( Nt recover( R R t do_rollback_twophase( R! Rt Rz ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt rollback_prepared� s c C� s | j j j | | d | �d S( NRz ( R R t do_commit_twophase( R! Rt Rz ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt commit_prepared� s c C� s5 | j d k r | j j � S| j d k o4 | j j S( s, Return True if a transaction is in progress.N( R R t in_transactionR t is_active( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR � s c C� s5 | j d k r | j j � S| j d k o4 | j j S( s, Return True if a transaction is in progress.N( R R t in_nested_transactionR R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� sO | j j d d � } t | d k pK | d k oK t | j j d d � d k � S( Nt isolation_levelt AUTOCOMMIT( R R; R t boolRf R R ( R! t opt_iso( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _is_autocommit_isolation� s c C� s# | j d k r | j j � S| j S( sa Return the current root transaction in progress, if any. .. versionadded:: 1.4 N( R R t get_transactionR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s# | j d k r | j j � S| j S( sc Return the current nested transaction in progress, if any. .. versionadded:: 1.4 N( R R t get_nested_transactionR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s� | j s t � | j rE | j � r5 | j d � qE | j d � n t | _ | j sc | j j rv | j j | � n zM y | j j j | j � Wn, t k r� } | j | d d d d � n XWd t | _ Xd S( Ns? BEGIN (implicit; DBAPI should not BEGIN due to autocommit mode)s BEGIN (implicit)( R R R R� R7 t TrueR R R R Rl R t do_beginR" R[ R\ R R ( R! t transactionR] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _begin_impl� s !c C� s� | j s t � | j s% | j j r8 | j j | � n | j r� | j rv | j � rf | j d � qv | j d � n y | j j j | j � Wq� t k r� } | j | d d d d � q� Xn d S( NsV ROLLBACK using DBAPI connection.rollback(), DBAPI should ignore due to autocommit modet ROLLBACK( R R R R R t rollbackRg R R� R7 R t do_rollbackR" R[ R\ R ( R! R] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _rollback_impl s c C� s� | j s t � | r3 | j � r3 t j d � n | j sH | j j r[ | j j | � n | j r� | j � r� | j d � q� | j d � n y | j j j | j � Wn, t k r� } | j | d d d d � n Xd S( Ns� The 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.sR COMMIT using DBAPI connection.commit(), DBAPI should ignore due to autocommit modet COMMIT( R R R� R Rr R R R t commitR R7 R t do_commitR" R[ R\ R ( R! t autocommitR] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _commit_impl* s c C� s� | j s t � | j s% | j j r; | j j | | � n | d k rf | j d 7_ d | j } n | j r� | j j j | | � | Sd S( Ni s sa_savepoint_%s( R R R R R t savepointR R Rg R t do_savepoint( R! R@ ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _savepoint_implJ s c C� sd | j s t � | j s% | j j r> | j j | | d � n | j r` | j j j | | � n d S( N( R R R R R t rollback_savepointR Rg R t do_rollback_to_savepoint( R! R@ ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _rollback_to_savepoint_implW s c C� sd | j s t � | j s% | j j r> | j j | | d � n | j r` | j j j | | � n d S( N( R R R R R t release_savepointR Rg R t do_release_savepoint( R! R@ ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _release_savepoint_impl` s c C� s� | j s t � | j r) | j d � n | j s> | j j rW | j j | | j � n | j r� t | _ zP y | j j j | | j � Wn, t k r� } | j | d d d d � n XWd t | _ Xn d S( Ns BEGIN TWOPHASE (implicit)( R R R R7 R R R Ru Rt Rg R� R R t do_begin_twophaseR[ R\ R R ( R! R� R] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _begin_twophase_impli s !c C� s� | j s t � | j s% | j j r; | j j | | � n | j r� t | j t � s\ t � y | j j j | | � Wq� t k r� } | j | d d d d � q� Xn d S( N( R R R R R t prepare_twophaseRg t isinstanceR Rw R t do_prepare_twophaseR[ R\ R ( R! Rt R] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _prepare_twophase_implz s c C� s� | j s t � | j s% | j j r> | j j | | | � n | j r� t | j t � s_ t � y | j j j | | | � Wq� t k r� } | j | d d d d � q� Xn d S( N( R R R R R t rollback_twophaseRg R� R Rw R R{ R[ R\ R ( R! Rt t is_preparedR] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _rollback_twophase_impl� s c C� s� | j s t � | j s% | j j r> | j j | | | � n | j r� t | j t � s_ t � y | j j j | | | � Wq� t k r� } | j | d d d d � q� Xn d S( N( R R R R R t commit_twophaseRg R� R Rw R R} R[ R\ R ( R! Rt R� R] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _commit_twophase_impl� s c C� s6 | j r | j j � n | j � s2 | j � n d S( N( R t _autorollbackR R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s t j d � d S( Ns 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.( R Rr ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _warn_for_legacy_exec_format� s c C� s� | j r< | j s t � t j d � d | _ t | _ d S| j r[ | j j � t } n t } | j d k r� | j } | r� | j d t � n | j � d | _ n t | _ d S( sf Close 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. s� The .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.Nt transaction_reset( R RD R R Rr R R R R R RL R� t _close_special( R! t skip_resett conn( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRL � s$ c O� s | j | | | � j � S( s� Executes and returns the first column of the first row. The underlying result/cursor is closed after execution. ( t executet scalar( R! t object_t multiparamst params( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c O� s | j | | | � j � S( s� 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 :class:`_result.ScalarResult` instance. :return: a :class:`_result.ScalarResult` .. versionadded:: 1.4.24 ( R� t scalars( R! R� R� R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c O� s� t | t j � r; t j d � | j | | | t d t �Sy | j } Wn/ t k ry } t j t j | � d | �n X| | | | t � Sd S( sY Executes a SQL statement construct and returns a :class:`_engine.CursorResult`. :param statement: The statement to be executed. May be one of: * a plain string (deprecated) * any :class:`_expression.ClauseElement` construct that is also a subclass of :class:`.Executable`, such as a :func:`_expression.select` construct * a :class:`.FunctionElement`, such as that generated by :data:`.func`, will be automatically wrapped in a SELECT statement, which is then executed. * a :class:`.DDLElement` object * a :class:`.DefaultGenerator` object * a :class:`.Compiled` object .. deprecated:: 2.0 passing a string to :meth:`_engine.Connection.execute` is deprecated and will be removed in version 2.0. Use the :func:`_expression.text` construct with :meth:`_engine.Connection.execute`, or the :meth:`_engine.Connection.exec_driver_sql` method to invoke a driver-level SQL string. :param \*multiparams/\**params: represent bound parameter values to be used in the execution. Typically, the format is either a collection of one or more dictionaries passed to \*multiparams:: conn.execute( table.insert(), {"id":1, "value":"v1"}, {"id":2, "value":"v2"} ) ...or individual key/values interpreted by \**params:: conn.execute( table.insert(), id=1, value="v1" ) In the case that a plain SQL string is passed, and the underlying DBAPI accepts positional bind parameters, a collection of tuples or individual values in \*multiparams may be passed:: conn.execute( "INSERT INTO table (id, value) VALUES (?, ?)", (1, "v1"), (2, "v2") ) conn.execute( "INSERT INTO table (id, value) VALUES (?, ?)", 1, "v1" ) Note above, the usage of a question mark "?" or other symbol is contingent upon the "paramstyle" accepted by the DBAPI in use, which may be any of "qmark", "named", "pyformat", "format", "numeric". See `pep-249 <https://www.python.org/dev/peps/pep-0249/>`_ 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. s� Passing 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.t futuret replace_contextN( R� R t string_typesRr t _exec_driver_sqlt _EMPTY_EXECUTION_OPTSR t _execute_on_connectiont AttributeErrort raise_R t ObjectNotExecutableError( R! t statementR� R� t metht err( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� s K c C� s | j | j � | | | � S( s% Execute a sql.FunctionElement object.( t _execute_clauseelementt select( R! t funcR� R� RT ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _execute_functionk s c C� s] | j j | � } t | | | � } | j s9 | j j r] | j | | | � \ } } } } n yL | j } | d k r� | j � } n | j } | j j | | | | � } WnK t j t j f k r� � n, t k r� } | j | d d d d � n X| j d | d � } | j r"| j � n | j s7| j j rY| j j | | | | | | � n | S( s& Execute a schema.ColumnDefault object.N( R t merge_withR R R t _invoke_before_exec_eventR R RX R t execution_ctx_clst _init_defaultR RY RZ R[ R\ t _exec_defaultR RL R t after_execute( R! t defaultR� R� RT t distilled_parameterst distilled_paramst event_multiparamst event_paramsR� R t ctxR] t ret( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _execute_defaultr s: c C� s | j j | j | � } t | | | � } | j s? | j j rc | j | | | � \ } } } } n | j j | � } | j d d � } | j } | j d | d | � } | j | | j j | d | | � } | j s� | j j r| j j | | | | | | � n | S( s Execute a schema.DDL object.R: R N( R R� R R R R� R; R R t compilet _execute_contextR� t _init_ddlR R� ( R! t ddlR� R� RT R� R� R� R� t exec_optsR: R t compiledR� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _execute_ddl� s6 c C� s� t | � d k r& g | d } } n | i } } x5 | j j D]' } | | | | | | � \ } } } q@ W| r� t | � } | r� t j d � � q� n | r� | g } n g } | | | | f S( Ni i sL Event handler can't return non-empty multiparams and params at the same time( t lenR t before_executet listR Ro ( R! t elemR� RT R� R� t fn( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s& c C� sx | j j | j | � } t | | | � } | j p< | j j } | ri | j | | | � \ } } } } n | r� t | d � } t | � d k } n g } t } | j } | j d d � } | j d | j j � } | j d | d | d | d | d | d | j j t j B� \ } } } | j | | j j | | | | | | | d | � } | rt| j j | | | | | | � n | S( s# Execute a sql.ClauseElement object.i i R: t compiled_cacheR t column_keyst for_executemanyt lintingt cache_hitN( R R� R R R R� t sortedR� R R R; R t _compiled_cachet _compile_w_cachet compiler_lintingR t WARN_LINTINGR� R� t _init_compiledR R� ( R! R� R� R� RT R� t has_eventsR� R� t keysR� R R: R� t compiled_sqlt extracted_paramsR� R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � sX c C� s� | j j | j | � } t | | | � } | j s? | j j rc | j | | | � \ } } } } n | j } | j | | j j | | | | | d d � } | j s� | j j r� | j j | | | | | | � n | S( si Execute a sql.Compiled object. TODO: why do we have this? likely deprecate or remove N( RT R� R R R R R� R R� R� R� R R R� ( R! R� R� R� RT R� R� R� R� R R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _execute_compiled@ s4 c C� s� | j j | � } t | | | � } | sf | j s? | j j rf | j | | | � \ } } } } qf n | j } | j | | j j | | | | | � } | s� | j s� | j j r� | j j | | | | | | � q� n | S( N( R R� R R R R� R R� R� t _init_statementR R� ( R! R� R� R� RT R� R� R� R� R� R R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� t s4 ! c C� sh t | � \ } } y | j } Wn/ t k rP } t j t j | � d | �n X| | | | | � Sd S( NR� ( R R� R� R R� R R� ( R! R� t parametersRT t args_10stylet kwargs_10styleR� R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _execute_20� s c C� s. t | � \ } } | j | | | | d t �S( sW Executes a string SQL statement on the DBAPI cursor directly, without any SQL compilation steps. This can be used to pass any string directly to the ``cursor.execute()`` method of the DBAPI in use. :param statement: The statement str to be executed. Bound parameters must use the underlying DBAPI's paramstyle, such as "qmark", "pyformat", "format", etc. :param parameters: represent bound parameter values to be used in the execution. The format is one of: a dictionary of named parameters, a tuple of positional parameters, or a list containing either dictionaries or tuples for multiple-execute support. :return: a :class:`_engine.CursorResult`. E.g. multiple dictionaries:: conn.exec_driver_sql( "INSERT INTO table (id, value) VALUES (%(id)s, %(value)s)", [{"id":1, "value":"v1"}, {"id":2, "value":"v2"}] ) Single dictionary:: conn.exec_driver_sql( "INSERT INTO table (id, value) VALUES (%(id)s, %(value)s)", dict(id=1, value="v1") ) Single tuple:: conn.exec_driver_sql( "INSERT INTO table (id, value) VALUES (?, ?)", (1, 'v1') ) .. note:: The :meth:`_engine.Connection.exec_driver_sql` method does not participate in the :meth:`_events.ConnectionEvents.before_execute` and :meth:`_events.ConnectionEvents.after_execute` events. To intercept calls to :meth:`_engine.Connection.exec_driver_sql`, use :meth:`_events.ConnectionEvents.before_cursor_execute` and :meth:`_events.ConnectionEvents.after_cursor_execute`. .. seealso:: :pep:`249` R� ( R R� R� ( R! R� R� RT R� R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt exec_driver_sql� s 8c O� s� | } | j r | j } n | r\ | j d d � } | r\ | j i t d 6| d 6� } q\ n yC | j } | d k r� | j � } n | | | | | | | � } WnT t j t j f k r� � n5 t k r� } | j | t j | � | d d � n X| j r | j j s"| j r/| j j r/| j � n | j rHt j | � n | j rm| j d k rm| j � n | j � | j r�| j � n | j | j | j } } } | j s�| d } n | j s�| j j rx; | j j! D]* } | | | | | | | j � \ } } q�Wn | j" r�| j# | � | j$ � } | j j% so| j# d | t& j' | d d d | j �� q�| j# d | f � n t( } y3| j r| j) j r�x9 | j) j j* D]% } | | | | | � r�t } Pq�q�Wn | s�| j) j* | | | | � q�n� | r|| j+ r|| j) j rZx6 | j) j j, D]" } | | | | � r1t } Pq1q1Wn | s�| j) j, | | | � q�nj | j) j r�x9 | j) j j- D]% } | | | | | � r�t } Pq�q�Wn | s�| j) j- | | | | � n | j s�| j j r | j j. | | | | | | j � n | j/ � | j0 � } | j s�| j1 } | j2 rd| rdt | _3 n | j d k r�| j4 r�| j5 d t � n | r�| j2 r�| j s�t6 � | j7 � q�n Wn, t k r�} | j | | | | | � n X| S( sd Create an :class:`.ExecutionContext` and execute, returning a :class:`_engine.CursorResult`.t yield_pert stream_resultst max_row_bufferi s [%s] %rt batchesi t ismultis8 [%s] [SQL parameters hidden due to hide_parameters=True]R� N(8 R R; R RQ R� R RX R RY RZ R[ R\ R t text_typeR R� R Rc t _trans_context_managerR t _trans_ctx_checkRD Rm t pre_exect use_setinputsizest _set_input_sizest cursorR� R� t executemanyR R R t before_cursor_executeR R7 t _get_cache_statst hide_parameterst sql_utilt _repr_paramsR R t do_executemanyt no_parameterst do_execute_no_paramst do_executet after_cursor_executet post_exect _setup_result_proxyR t _soft_closedt _autoclose_connectiont should_autocommitR� R RL ( R! R t constructorR� R� RT t argsR5 t branchedt ypR� t contextR] R R� t statst evt_handledt resultR ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s� c C� sE | j s | j j rP x8 | j j D]' } | | | | | | t � \ } } q" Wn | j ry | j | � | j d | � n yb x[ | j j s� d n | j j j D] } | | | | | � r� Pq� q� W| j j | | | | � Wn, t k r } | j | | | | | � n X| j s | j j rA| j j | | | | | t � n d S( s_ 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(). s [raw sql] %rN( ( R R R R R R R7 R R R[ R\ R ( R! R R� R� R R� R] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _cursor_execute� s( % c C� sB y | j � Wn- t k r= | j j j j d d t �n Xd S( s\ Close the given cursor, catching exceptions and turning into log warnings. s Error closing cursort exc_infoN( RL t ExceptionR t poolR1 t errorR� ( R! R ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _safe_close_cursor� s c C� s t j � } t j | � } | j s� t | | j j j � rp | j rp | j j | | j sd | j n d | � p} | o} | j | _ n | } | j rt j t j j | | | | j j j d | j j d | j d | d k r� | j n d �d | d d | �n t | _ zot | | j j j � pD| d k oD| d k oD| } | r�t j j | | | | j j j d | j j d | j d | j d | d k r�| j n d �} n d } d } | j s�| j j r�| j j d t � r�t | | | j | | | | | | j | � } x] | j j D]O } y, | | � } | d k rO| | _ } n Wq t k rl} | } Pq Xq W| j | j k r�| j | _ | r�| j | _ q�n | j! } n | r�| r�| j" | � n | j s| r�| j# | � n t j$ d t � � | j% � Wd QXn | r:t j | d | d d | �nA | r`t j | d | d d | �n t j | d d | d �Wd | ` | j r�| ` | j s�| j } | r�| j j& j' | | � n | j( | � q�n | j) r�| j* s�t+ � | j, � n Xd S( NR R R� t with_tracebacki t from_t connection_invalidatedt skip_user_error_eventst warn_onlyi (- t sysR R t is_exit_exceptiont _is_disconnectR� R t dbapit ErrorRV t is_disconnectRW R R t _reentrant_errorR� R t DBAPIErrort instanceR R R R� R R R; R t ExceptionContextImplR t handle_errort chained_exceptionR R" t invalidate_pool_on_disconnectt handle_dbapi_exceptionR t safe_reraiseR� R t _invalidateRj R RD R RL ( R! R] R� R� R R R R& R1 t should_wrapt sqlalchemy_exceptiont newraiseR� R� t per_fnt _raisedt dbapi_conn_wrapper( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR\ � s� c C� s� t j � } | j | d d � } t | | j j � } | ro t j j d d | | j j d | j d | �} n d } d } | j r6t | | | d d d d d | t � } x] | j j D]O } y, | | � } | d k r� | | _ } n Wq� t k r} | } Pq� Xq� W| r6| | j k r6| j | _ } q6n | r\t j | d | d d | �nA | r�t j | d | d d | �n t j | d d | d �d S( NR R" R i R! i ( R% R R* R R� R( R) R R, R- R R R. R� R R/ R0 R R" R R� ( t clsR] R R R R* R5 R6 R7 R� R� R8 R9 ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt$ _handle_dbapi_exception_noconnectioni sR c K� s | | j | | � j | � d S( s� 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. N( R t traverse_single( R! t visitorcallablet elementt kwargs( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _run_ddl_visitor� s s 1.4s� The :meth:`_engine.Connection.transaction` method is deprecated and will be removed in a future release. Use the :meth:`_engine.Engine.begin` context manager instead.c O� sh t | d <| j � } y' | j | | | � } | j � | SWn$ t j � � | j � Wd QXn Xd S( st Execute 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� Rl t run_callableR� R R3 R� ( R! t callable_R R@ t transR� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s 1 s� The :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 O� s | | | | � S( s� Given 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. ( ( R! RD R R@ ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRC � s (W t __name__t __module__t __doc__R RD t _sqla_logger_namespaceR R� R� R' R t memoized_propertyR- R7 R9 t propertyR< RA RC RJ RK RP RT RU RV RW R" R^ R_ Rc RX Rg R2 t deprecated_20Rh Rj Rk Rm Rl Rq Ru Ry R| R~ R R� R� R� R� R� R� R� R� R� R� R� R� R� R� R� R� RL R� R� R� R� R� R� R� R� R� R� R� R� R� R� R R R+ R' R\ t classmethodR< RA t deprecatedR� RC ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR s� . � , ; M E 7 e 2 . M / / A � ( �= 9R. c B� s e Z d Z d � Z RS( s3 Implement the :class:`.ExceptionContext` interface.c C� sU | | _ | | _ | | _ | | _ | | _ | | _ | | _ | | _ | | _ d S( N( R R" R6 t original_exceptiont execution_contextR� R� R* R1 ( R! Ri R6 R R" R R� R� R R* R1 ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' s ( RF RG RH R' ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR. s t Transactionc B� s� e Z d Z d Z e Z d � Z d � Z e d � � Z d � Z d � Z d � Z e d � � Z d � Z d � Z d � Z d � Z d � Z d � Z d � Z RS( st Represent 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 c C� s t � � d S( N( t NotImplementedError( R! R" ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' E s c C� s t � � d S( s do 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. N( RR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _do_deactivateH s c C� s t � � d S( s� True if this transaction is totally deactivated from the connection and therefore can no longer affect its state. N( RR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _deactivated_from_connectionY s c C� s t � � d S( N( RR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _do_closea s c C� s t � � d S( N( RR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _do_rollbackd s c C� s t � � d S( N( RR ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _do_commitg s c C� s | j o | j j S( N( R� R" RW ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRe j s c C� s& z | j � Wd | j s! t � Xd S( s; 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( RU R� R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRL n s c C� s& z | j � Wd | j s! t � Xd S( s� 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( RV R� R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� ~ s c C� s& z | j � Wd | j s! t � Xd S( s� 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 phase transactions may be used. N( RW R� R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s | j S( N( R" ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _get_subject� s c C� s | j S( N( R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _transaction_is_active� s c C� s | j S( N( RT ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _transaction_is_closed� s c C� s t S( N( R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _rollback_can_be_called� s ( ( RF RG RH t __slots__R t _is_rootR' RS RK RT RU RV RW Re RL R� R� RX RY RZ R[ ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRQ s" # Rp c B� s_ e Z d Z d Z d � Z e d � � Z e d � � Z d � Z d � Z d � Z d � Z RS( s� A 'marker' transaction that is used for nested begin() calls. .. deprecated:: 1.4 future connection for 2.0 won't support this pattern. R" t _is_activeR c C� s� | j d k s t � | j j s3 t j d � � n | j sC t � t j d � | | _ | j rr t j | � n | j d k r� | j | _ n | j | _ t | _ d S( NsW the current transaction on this connection is inactive. Please issue a rollback first.s� Calling .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.( R R R R� R Ro RD R Rr R" R� R R� R R� R^ ( R! R" ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' � s c C� s | j S( N( R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRT � s c C� s | j o | j j S( N( R^ R R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s t | _ d S( N( R R^ ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _deactivate� s c C� s | j � d S( N( R_ ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRU � s c C� s/ | j r+ z | j j � Wd | j � Xn d S( N( R^ R RS R_ ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRV � s c C� s | j � d S( N( R_ ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRW � s ( R" R^ R ( RF RG RH R\ R' RK RT R� R_ RU RV RW ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRp � s Rn c B� s� e Z d Z e Z d Z d � Z d � Z e d � � Z d � Z d � Z d � Z d � Z e d � Z d � Z d � Z d � Z RS( s� Represent 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. R" R� c C� sW | j d k s t � | j r. t j | � n | | _ | j � | | _ t | _ d S( N( R R R R� R R� R" t _connection_begin_implR� R� ( R! R" ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' s c C� sS | j r- | j j | k s! t � t | _ n" | j j | k rO t j d � n d S( Ns0 transaction already deassociated from connection( R� R" R R R R t warn( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _deactivate_from_connection s c C� s | j j | k S( N( R" R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRT & s c C� s[ | j j | k s t � | j r. | j � n | j j rM | j j j � n | j � d S( N( R" R R R� t _connection_rollback_implR t _cancelRb ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRS * s c C� s | j j | � d S( N( R" R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR` ? s c C� s | j j � d S( N( R" R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRc B s c C� s | j j � d S( N( R" R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _connection_commit_implE s c C� s� z9 | j r | j � n | j j r8 | j j j � n Wd | j sK | rX | j � n | j j | k ry d | j _ n X| j s� t � | j j | k s� t � d S( N( R� Rc R" R Rd Rb R R R ( R! t try_deactivate( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _close_implH s c C� s | j � d S( N( Rg ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRU X s c C� s | j d t � d S( NRf ( Rg R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRV [ s c C� s� | j rk | j j | k s! t � z | j � Wd | j j rQ | j j j � n | j � Xd | j _ n1 | j j | k r� | j j � n t j d � � | j s� t � | j j | k s� t � d S( Ns This transaction is inactive( R� R" R R Re R Rd Rb R Rc R Ro ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRW ^ s ( R" R� ( RF RG RH R� R] R\ R' Rb RK RT RS R` Rc Re R Rg RU RV RW ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRn � s Rs c B� sn e Z d Z d Z d � Z e d � Z e d � � Z d � Z d � Z d � Z d � Z d � Z d � Z RS( s� Represent 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� t _savepointt _previous_nestedc C� sk | j d k s t � | j r. t j | � n | | _ | j j � | _ t | _ | j | _ | | _ d S( N( R R R R� R R� R" R� Rh R� R� R Ri ( R! R" ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' � s c C� s> | j j | k r$ | j | j _ n | r: t j d � n d S( Ns7 nested transaction already deassociated from connection( R" R Ri R Ra ( R! Ra ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRb � s c C� s | j j | k S( N( R" R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRT � s c C� s0 t | _ | j � | j r, | j j � n d S( N( R R� Rb Ri Rd ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRd � s c C� s� z2 | j r1 | j j j r1 | j j | j � n Wd t | _ | rW | j d | � n X| j sh t � | r� | j j | k s� t � n d S( NRa ( R� R" R R� Rh R Rb R R ( R! t deactivate_from_connectiont warn_already_deactive( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRg � s c C� s | j t t � d S( N( Rg R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRS � s c C� s | j t t � d S( N( Rg R� R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRU � s c C� s | j t t � d S( N( Rg R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRV � s c C� so | j r: z | j j | j � Wd t | _ X| j � n1 | j j | k r\ | j j � n t j d � � d S( Ns# This nested transaction is inactive( R� R" R� Rh R Rb R Rc R Ro ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRW � s ( R" R� Rh Ri ( RF RG RH R\ R' R� Rb RK RT Rd Rg RS RU RV RW ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRs { s Rw c B� sA e Z d Z d Z d � Z d � Z d � Z d � Z d � Z RS( s Represent 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" R� Rt t _is_preparedc C� s, t | _ | | _ t t | � j | � d S( N( R Rl Rt t superRw R' ( R! R" Rt ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' � s c C� s; | j s t j d � � n | j j | j � t | _ d S( sq Prepare this :class:`.TwoPhaseTransaction`. After a PREPARE, the transaction can be committed. s This transaction is inactiveN( R� R Ro R" R� Rt R� Rl ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt prepare� s c C� s | j j | � d S( N( R" R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR` s c C� s | j j | j | j � d S( N( R" R� Rt Rl ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRc s c C� s | j j | j | j � d S( N( R" R� Rt Rl ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRe s ( R" R� Rt Rl ( RF RG RH R\ R' Rn R` Rc Re ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRw � s t Enginec B� s e Z d Z e Z e Z e Z d Z e Z d) Z d) d) d d) e d � Z d � Z e d � � Z d � Z d � Z d � Z d � Z e d � � Z e d � � Z e j � Z d � Z e d � Z d* e j d � Z e j! d) d � � Z" d e# f d � � YZ$ e d � Z% e j& d d � d � � Z' e j& d d � d � � Z( d � Z) e j* d d d �d � � Z+ e j* d d d �d � � Z, d) d) e d � Z- e d! � Z. e d" � Z/ e j& d d# � d) d) d$ � � Z0 e j& d d% � d) d& � � Z1 d' � Z2 d) d( � Z3 RS(+ s9 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` s sqlalchemy.engine.Enginei� c C� s� | | _ | | _ | | _ | r- | | _ n | | _ | | _ | d k ri t j | d | j �| _ n d | _ t j | d | �| r� | j | � n d S( Ni t size_alertt echoflag( R t urlR t logging_namet echoR R t LRUCachet _lru_size_alertR� R R t instance_loggert update_execution_options( R! R R Rr Rs Rt t query_cache_sizeRT R ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' , s c C� s/ | j r+ | j j d t | � | j � n d S( Nsi Compiled cache size pruning from %d items to %d. Increase cache size to reduce the frequency of pruning.( R R1 R2 R� t capacity( R! t cache( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRv H s c C� s | S( N( ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR Q s c C� s | j r | j j � n d S( s� 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 :paramref:`.Connection.execution_options.query_cache` parameter. .. versionadded:: 1.4 N( R� t clear( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt clear_compiled_cacheU s c K� s? | j j | � | _ | j j | | � | j j | | � d S( s� 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( R RQ R t set_engine_execution_optionsR ( R! RS ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRx c s c K� s | j | | � S( s� Return 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 "sharding" schemes where multiple :class:`_engine.Engine` objects refer to the same connection pool, but are differentiated by options that would be consumed by a custom event:: primary_engine = create_engine("mysql://") shard1 = primary_engine.execution_options(shard_id="shard1") shard2 = primary_engine.execution_options(shard_id="shard2") Above, the ``shard1`` engine serves as a factory for :class:`_engine.Connection` objects that will contain the execution option ``shard_id=shard1``, and ``shard2`` will produce :class:`_engine.Connection` objects that contain the execution option ``shard_id=shard2``. An event handler can consume the above execution option to perform a schema switch or other operation, given a connection. Below we emit a MySQL ``use`` statement to switch databases, at the same time keeping track of which database we've established using the :attr:`_engine.Connection.info` dictionary, which gives us a persistent storage space that follows the DBAPI connection:: from sqlalchemy import event from sqlalchemy.engine import Engine shards = {"default": "base", shard_1: "db1", "shard_2": "db2"} @event.listens_for(Engine, "before_cursor_execute") def _switch_shard(conn, cursor, stmt, params, context, executemany): shard_id = conn._execution_options.get('shard_id', "default") current_shard = conn.info.get("current_shard", None) if current_shard != shard_id: cursor.execute("use %s" % shards[shard_id]) conn.info["current_shard"] = shard_id .. 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` ( t _option_cls( R! RS ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRT x s Jc C� s | j S( s� Get the non-SQL options which will take effect during execution. .. versionadded: 1.3 .. seealso:: :meth:`_engine.Engine.execution_options` ( R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRU � s c C� s | j j S( si String name of the :class:`~sqlalchemy.engine.interfaces.Dialect` in use by this :class:`Engine`.( R R@ ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR@ � s c C� s | j j S( si Driver name of the :class:`~sqlalchemy.engine.interfaces.Dialect` in use by this :class:`Engine`.( R t driver( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s d | j f S( Ns Engine(%r)( Rr ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt __repr__� s c C� s< | r | j j � n | j j � | _ | j j | � d S( s Dispose 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 process. .. seealso:: :ref:`engine_disposal` :ref:`pooling_multiprocessing` N( R t disposet recreateR t engine_disposed( R! RL ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s %c C� s, | j � � } | j | | | � SWd QXd S( N( Rh R� ( R! R� R� R� R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� s c c� s2 | d k r) | j � � } | VWd QXn | Vd S( N( R Rh ( R! R" R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _optional_conn_ctx_manager s t _trans_ctxc B� s# e Z d � Z d � Z d � Z RS( c C� s | | _ | | _ | | _ d S( N( R� R� R# ( R! R� R� R# ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' s c C� s | j j � | j S( N( R� RK R� ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRK s c C� s; z | j j | | | � Wd | j s6 | j j � n Xd S( N( R� RP R# R� RL ( R! RM RN RO ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRP $ s ( RF RG R' RK RP ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� s c C� sw | j j r | j � } n | j d | � } y | j � } Wn$ t j � � | j � Wd QXn Xt j | | | � S( sX Return 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( RB RD Rh Rl R R3 RL Ro R� ( R! R# R� RE ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRl + s # s 1.4s� The :meth:`_engine.Engine.transaction` method is deprecated and will be removed in a future release. Use the :meth:`_engine.Engine.begin` context manager instead.c O� s6 t | d <| j � � } | j | | | � SWd QXd S( s Execute 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` RB N( R� Rh R� ( R! RD R R@ R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� Y s / s� The :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.c O� s6 t | d <| j � � } | j | | | � SWd QXd S( s� Given 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. RB N( R� Rh RC ( R! RD R R@ R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRC � s c K� s, | j � � } | j | | | � Wd QXd S( N( Rl RA ( R! R> R? R@ R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRA � s s :meth:`_engine.Engine.execute`t alternatives� 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`.c O� s% | j d t � } | j | | | � S( s� Executes 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. R# ( Rh R� R� ( R! R� R� R� R" ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s s :meth:`_engine.Engine.scalar`s' 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.c O� s | j | | | � j � S( s� Executes and returns the first column of the first row. The underlying result/cursor is closed after execution. ( R� R� ( R! R� R� R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s( | j d t � } | j | | | | � S( NR# ( Rh R� R� ( R! R� R� R� RT R" ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s( | j d t � } | j | | | | � S( NR# ( Rh R� R� ( R! R� R� R� RT R" ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s c C� s | j | d | �S( s� Return 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`. R# ( RB ( R! R# ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRh � s s� The :meth:`_engine.Engine.table_names` method is deprecated and will be removed in a future release. Please refer to :meth:`_reflection.Inspector.get_table_names`.c C� s8 | j | � �# } t j | � } | j | � SWd QXd S( s� Return a list of all table names available in the database. :param schema: Optional, retrieve names from a non-default schema. :param connection: Optional, use a specified connection. N( R� R t inspectt get_table_names( R! R= R" R� t insp( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt table_names� s s� The :meth:`_engine.Engine.has_table` method is deprecated and will be removed in a future release. Please refer to :meth:`_reflection.Inspector.has_table`.c C� s> | j d � �) } t j | � } | j | d | �SWd QXd S( s` Return True if the given backend has a table of the given name. .. seealso:: :ref:`metadata_reflection_inspector` - detailed schema inspection using the :class:`_reflection.Inspector` interface. :class:`.quoted_name` - used to pass quoting information along with a schema identifier. R= N( R� R R R� t has_table( R! t table_nameR= R� R� ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� s c C� s} | j } y | � SWnb | j j k rx } | d k rN t j | | | � qy t j t j � d d t j � d �n Xd S( Ni R i ( R R( R) R R R< R R� R% R ( R! R� R" R R] ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _wrap_pool_connect( s c C� s | j | j j | � S( sC Return 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 Rh ( R! Rd ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR 6 s N( (4 RF RG RH R� R R R R RB RI RD R R< R' Rv RK R R} Rx RT RU R@ R� R t echo_propertyRt R� R� R� R t EMPTY_DICTR� t contextlibt contextmanagerR� t objectR� Rl RN R� RC RA RL R� R� R� R� Rh R� R� R� R ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyRo sp L + .1 t OptionEngineMixinc B� sY e Z e Z d � Z d � Z d � Z e e e � Z d � Z d � Z e e e � Z RS( c C� s� | | _ | j | _ | j | _ | j | _ | j | _ | j | _ | j | _ t j | d | j �| j j | j � | _ | j | _ | j | � d S( NRq ( t _proxiedRr R Rs Rt R� R R Rw R R R Rx ( R! t proxiedRT ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR' R s c C� s | j j S( N( R� R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _get_poolm s c C� s | | j _ d S( N( R� R ( R! R ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _set_poolp s c C� s | j j p | j j d t � S( NR ( R� R RG R; R ( R! ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _get_has_eventsu s c C� s | | j d <d S( NR ( RG ( R! RN ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt _set_has_eventsz s ( RF RG R t _sa_propagate_class_eventsR' R� R� RK R R� R� R ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� O s t OptionEnginec B� s e Z RS( ( RF RG ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyR� � s (! t __future__R R� R% t interfacesR R R R R R R, R R R t sqlR R t immutabledictR� R R. RQ Rp Rn Rs Rw t IdentifiedRo R� R� R� R ( ( ( sI /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/engine/base.pyt <module> sF � � � � � � � � ��@�m' � � B1