B

��4]�H
�@s
dd
lm
Z

ddlZddlZddlmZ
ddlmZ
ddlmZ
ddl	m
Z

dd	l	mZ
dd
l	mZ
ddl	mZ
ddlm
Z

ddlmZ
Gd
d�de�ZGdd�de�ZGdd�de�ZGdd�de�ZGdd�de�ZGdd�de�ZGdd�deej�ZGdd�de�ZdS)�)
�with_statementN�
)
�Connectable)
�ExceptionContext)
�_distill_params�)
�exc)
�
interfaces)
�log)
�util)
�schemac@seZ
dZd
Ze�d�
Zdtdd�
Zdd�Ze	dd	��
Z
d
d�Zdd
�Zdd�Z
dd�Zdd�Ze	dd��
Ze	dd��
Ze	dd��
Zdd�Ze	dd��
Zdd�Ze	d d!��
Ze	d"d#��
Ze	d$d%��
Zd&d'�Zd(d)�Zdud*d+�
Zd,d-�Zd.d/�Zd0d1�Zdvd2d3�
Zd4d5�Z dwd6d7�
Z!dxd8d9�
Z"d:d;�Z#d<d=�Z$d>d?�Z%dyd@dA�
Z&dzdBdC�
Z'dDdE�Z(dFdG�Z)dHdI�Z*dJdK�Z+dLdM�Z,dNdO�Z-dPdQ�Z.dRdS�Z/dTdU�Z0dVdW�Z1dXdY�Z2dZd[�Z3d\d]�Z4d^d_�Z5d`da�Z6dbdc�Z7ddde�Z8d{dfdg�
Z9dhdi�Z:dZ;dZ<djdk�Z=e>dldm��
Z?dndo�Z@dpdq�ZAdrds�ZBdS)|�
Connectiona:Provides high-level functionality for a wrapped DB-API connection.

    Provides execution support for string-based SQL statements as well as
    :class:`.ClauseElement`, :class:`.Compiled` and :class:`.DefaultGenerator`
    objects. Provides a :meth:`begin` method to return :class:`.Transaction`
    objects.

    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

    NFcCs�|
|_|
j
|_
||_|d
k	|_|rT||_||_|j|_d|_||_|j	|_	|j
|_
n||d
k	r`|n|
��|_d
|_d|_
||_d|_d|_|j��|_|d
kr�|j�|
j�
|_|p�|d
ko�|
j	|_	|r�t�
|
j|_|j	s�|jj	r�|j�||j�
d
S)z�Construct a new Connection.

        The constructor here is not public and is only called only by an
        :class:`.Engine`. See :meth:`.Engine.connect` and
        :meth:`.Engine.contextual_connect` methods.

        NFr
T)�engine�dialect�_Connection__branch_fromZ_Connection__branch�_Connection__connection�_execution_options�_echo�should_close_with_result�dispatch�_has_events�schema_for_object�raw_connection�_Connection__transaction�_Connection__savepoint_seq�_Connection__invalid�_Connection__can_reconnectZ_should_log_info�_join�AssertionErrorZengine_connect)�selfr�
connection�close_with_result�_branch_fromr�	_dispatchr�r$�I/opt/alt/python37/lib64/python3.7/site-packages/sqlalchemy/engine/base.py�__init__Es8






















zConnection.__init__c

Cs6|jr|j�
�S|jj|j|j||j|j|jd
�SdS)a�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.

        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() or
        contextual_connect() methods are called.  The branched connection
        acts as much as possible like the parent, except that it stays
        connected when a close() event occurs.

        )r"rrr#N)r�_branchr�_connection_clsrrrr)
rr$r$r%r's







zConnection._branchc


Cs|jr|jS|Sd
S)z�return the 'root' connection.

        Returns 'self' if this connection is not a branch, else
        returns the root connection from which we ultimately branched.

        N)
r)
rr$r$r%�_root�s	
zConnection._rootc
Cs|j�
|j�
}
|j��|
_|
S)
z3Create a shallow copy of this Connection.

        )�	__class__�__new__�__dict__�copy)r�
cr$r$r%�_clone�s

zConnection._clonec


Cs|S)
Nr$)
rr$r$r%�	__enter__�s
zConnection.__enter__cCs|��
dS)
N)
�close)r�type_�value�	tracebackr$r$r%�__exit__�s
zConnection.__exit__c
KsD|��}|j
�|
�
|_
|js$|jjr2|j�||
�
|j�||
�
|S)
a% Set non-SQL options for the connection which take effect
        during execution.

        The method returns a copy of this :class:`.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:`.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:`.Connection.execution_options`, and it will be stored in the
        ``_execution_options`` dictionary of the :class:`.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:`.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 DBAPI
          connections by default are always in a transaction - SQLAlchemy uses
          rules applied to different kinds of statements to determine if
          COMMIT will be invoked in order to provide its "autocommit" feature.
          Typically, all INSERT/UPDATE/DELETE statements as well as
          CREATE/DROP statements have autocommit behavior enabled; SELECT
          constructs do not. Use this option when invoking a SELECT or other
          specific SQL construct where COMMIT is desired (typically when
          calling stored procedures and such), and an explicit
          transaction is not in progress.

        :param compiled_cache: Available on: Connection.
          A dictionary where :class:`.Compiled` objects
          will be cached when the :class:`.Connection` compiles a clause
          expression into a :class:`.Compiled` object.
          It is the user's responsibility to
          manage the size of this dictionary, which will have keys
          corresponding to the dialect, clause element, the column
          names within the VALUES or SET clause of an INSERT or UPDATE,
          as well as the "batch" mode for an INSERT or UPDATE statement.
          The format of this dictionary is not guaranteed to stay the
          same in future releases.

          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 isolation_level: Available on: :class:`.Connection`.
          Set the transaction isolation level for
          the lifespan of this :class:`.Connection` object (*not* the
          underlying DBAPI connection, for which the level is reset
          to its original setting upon termination of this
          :class:`.Connection` object).

          Valid values include
          those string values accepted by the
          :paramref:`.create_engine.isolation_level`
          parameter passed to :func:`.create_engine`.  These levels are
          semi-database specific; see individual dialect documentation for
          valid levels.

          Note that this option necessarily affects the underlying
          DBAPI connection for the lifespan of the originating
          :class:`.Connection`, and is not per-execution. This
          setting is not removed until the underlying DBAPI connection
          is returned to the connection pool, i.e.
          the :meth:`.Connection.close` method is called.

          .. warning::  The ``isolation_level`` execution option should
             **not** be used when a transaction is already established, that
             is, the :meth:`.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.

             .. versionchanged:: 0.9.9 A warning is emitted when the
                ``isolation_level`` execution option is used after a
                transaction has been started with :meth:`.Connection.begin`
                or similar.

          .. note:: The ``isolation_level`` execution option is implicitly
             reset if the :class:`.Connection` is invalidated, e.g. via
             the :meth:`.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:`.create_engine.isolation_level`
                - set per :class:`.Engine` isolation level

                :meth:`.Connection.get_isolation_level` - view current 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.  This is a limitation
          of many DBAPIs.  The flag is currently understood only by the
          psycopg2, mysqldb and pymysql dialects.

        :param schema_translate_map: Available on: Connection, Engine.
          A dictionary mapping schema names to schema names, that will be
          applied to the :paramref:`.Table.schema` element of each
          :class:`.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.execution_options`

            :meth:`.Executable.execution_options`

            :meth:`.Connection.get_execution_options`


        )r/r�unionrrrZ set_connection_execution_optionsr)r�optr.r$r$r%�execution_options�s




zConnection.execution_optionsc


Cs|jS)
z� Get the non-SQL options which will take effect during execution.

        .. versionadded:: 1.3

        .. seealso::

            :meth:`.Connection.execution_options`
        )
r)
rr$r$r%�get_execution_optionsX
s	z Connection.get_execution_optionsc

Csd
|jko|j
S)z)Return True if this connection is closed.r)r,r)
rr$r$r%�closedc
s

zConnection.closedc


Cs|jj
S)
z/Return True if this connection was invalidated.)r)r)
rr$r$r%�invalidatedl
szConnection.invalidatedc

Cs^y|jSt
k
r


YnXy|��Stk
rX
}

z|�|
d
d
d
d
�
Wd
d
}
~
XYnXd
S)z�The underlying DB-API connection managed by this Connection.

        .. seealso::


            :ref:`dbapi_connections`

        N)r�AttributeError�_revalidate_connection�
BaseException�_handle_dbapi_exception)r�
er$r$r%r r
s





zConnection.connectionc

CsHy|j�
|j�
Stk
rB
}

z|�|
d
d
d
d
�
Wd
d
}
~
XYnXd
S)a�Return the current isolation level assigned to this
        :class:`.Connection`.

        This will typically be the default isolation level as determined
        by the dialect, unless if the
        :paramref:`.Connection.execution_options.isolation_level`
        feature has been used to alter the isolation level on a
        per-:class:`.Connection` basis.

        This attribute will typically perform a live SQL operation 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.  Compare to the
        :attr:`.Connection.default_isolation_level` accessor
        which returns the dialect-level setting without performing a SQL
        query.

        .. versionadded:: 0.9.9

        .. seealso::

            :attr:`.Connection.default_isolation_level` - view default level

            :paramref:`.create_engine.isolation_level`
            - set per :class:`.Engine` isolation level

            :paramref:`.Connection.execution_options.isolation_level`
            - set per :class:`.Connection` isolation level

        N)r�get_isolation_levelr r>r?)rr@r$r$r%rA�
s


zConnection.get_isolation_levelc


Cs|jj
S)
a�The default isolation level assigned to this :class:`.Connection`.

        This is the isolation level setting that the :class:`.Connection`
        has when first procured via the :meth:`.Engine.connect` method.
        This level stays in place until the
        :paramref:`.Connection.execution_options.isolation_level` is used
        to change the setting on a per-:class:`.Connection` basis.

        Unlike :meth:`.Connection.get_isolation_level`, this attribute is set
        ahead of time from the first connection procured by the dialect,
        so SQL query is not invoked when this accessor is called.

        .. versionadded:: 0.9.9

        .. seealso::

            :meth:`.Connection.get_isolation_level` - view current level

            :paramref:`.create_engine.isolation_level`
            - set per :class:`.Engine` isolation level

            :paramref:`.Connection.execution_options.isolation_level`
            - set per :class:`.Connection` isolation level

        )r�default_isolation_level)
rr$r$r%rB�
sz"Connection.default_isolation_levelc

CsZ|jr|j�
�S|jrL|jrL|jdk	r0t�d
�
�
|jj|d�
|_	d|_|j	St�
d�
�
dS)Nz8Can't reconnect until invalid transaction is rolled back)
�_connectionFzThis Connection is closed)rr=rrrr�InvalidRequestErrorrrr�ResourceClosedError)
rr$r$r%r=�
s










z!Connection._revalidate_connectionc

Cst|j
d
d�S)N�is_validF)�getattrr)
rr$r$r%�_connection_is_valid�
szConnection._connection_is_validc

Cs|jo|j
ot|jd
d�S)NrFF)r:r;rGr)
rr$r$r%�#_still_open_and_connection_is_valid�
s

z.Connection._still_open_and_connection_is_validc


Cs|jj
S)
a�
Info dictionary associated with the underlying DBAPI connection
        referred to by this :class:`.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:`.Connection`.

        )r �info)
rr$r$r%rJ�
szConnection.infoc

Cs|��S)
ai
Returns a branched version of this :class:`.Connection`.

        The :meth:`.Connection.close` method on the returned
        :class:`.Connection` can be called and this
        :class:`.Connection` will remain open.

        This method provides usage symmetry with
        :meth:`.Engine.connect`, including for usage
        with context managers.

        )
r')
rr$r$r%�connect�
s
zConnection.connectc
Ks|��S)
N)
r')r�kwargsr$r$r%�_contextual_connects
zConnection._contextual_connectcCsB|jr
d
S|j
rt�d�
�
|jjr0|jj�|
�

|j`d|j_d
S)a�Invalidate the underlying DBAPI connection associated with
        this :class:`.Connection`.

        The underlying DBAPI connection is literally closed (if
        possible), and is discarded.  Its source connection pool will
        typically lazily create a new connection to replace it.

        Upon the next use (where "use" typically means using the
        :meth:`.Connection.execute` method or similar),
        this :class:`.Connection` will attempt to
        procure a new DBAPI connection using the services of the
        :class:`.Pool` as a source of connectivity (e.g. a "reconnection").

        If a transaction was in progress (e.g. the
        :meth:`.Connection.begin` method has been called) when
        :meth:`.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:`.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:`.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:`.Connection.invalidate` method, just like auto-invalidation,
        will at the connection pool level invoke the
        :meth:`.PoolEvents.invalidate` event.

        .. seealso::

            :ref:`pool_connection_invalidation`

        NzThis Connection is closedT)	r;r:rrEr)rHr�
invalidater)r�	exceptionr$r$r%rNs'





zConnection.invalidatec

Cs|j�
�
d
S)aDetach the underlying DB-API connection from its connection pool.

        E.g.::

            with engine.connect() as conn:
                conn.detach()
                conn.execute("SET search_path TO schema1, schema2")

                # work with connection

            # connection is fully closed (since we used "with:", can
            # also call .close())

        This :class:`.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�detach)
rr$r$r%rP9szConnection.detachc

Cs:|jr|j�
�S|jd
kr*t|�
|_|jSt||j�Sd
S)a4Begin 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.

        Nested calls to :meth:`.begin` on the same :class:`.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.

        .. seealso::

            :meth:`.Connection.begin_nested` - use a SAVEPOINT

            :meth:`.Connection.begin_twophase` -
            use a two phase /XID transaction

            :meth:`.Engine.begin` - context manager available from
            :class:`.Engine`

        N)r�beginr�RootTransaction�Transaction)
rr$r$r%rQTs#





zConnection.beginc

Cs:|jr|j�
�S|jd
kr&t|�
|_nt||j�|_|jS)a+Begin a nested transaction and return a transaction handle.

        The returned object is an instance of :class:`.NestedTransaction`.

        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.

        .. seealso::

            :meth:`.Connection.begin`

            :meth:`.Connection.begin_twophase`

        N)r�begin_nestedrrR�NestedTransaction)
rr$r$r%rT�s




zConnection.begin_nestedcCsN|jr|jj
|
d
�
S|jdk	r(t�d�
�
|
dkr<|jj��}
t||
�|_|jS)aBegin 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:`.Connection.begin`

            :meth:`.Connection.begin_twophase`

        )
�xidNzOCannot start a two phase transaction when a transaction is already in progress.)	r�begin_twophaserrrDrrZ
create_xid�TwoPhaseTransaction)rrVr$r$r%rW�s






zConnection.begin_twophasec

Cs|jj
�|�
S)
N)rrZdo_recover_twophase)
rr$r$r%�recover_twophase�s
zConnection.recover_twophasecCs|jj
j||
|d
�
dS)N)
�recover)rr�do_rollback_twophase)rrVrZr$r$r%�rollback_prepared�s
zConnection.rollback_preparedcCs|jj
j||
|d
�
dS)N)
rZ)rr�do_commit_twophase)rrVrZr$r$r%�commit_prepared�s
zConnection.commit_preparedc

Cs|jj
d
k	S)z,Return True if a transaction is in progress.N)r)r)
rr$r$r%�in_transaction�szConnection.in_transactionc
Cs�|jr
t
�
|jr|jj�d
�

|js,|jjr8|j�|�

y(|jj	�
|j�

|jjdkr^|
|j_Wn4t
k
r�
}
z|�|dddd�
Wdd}~XYnXdS)NzBEGIN (implicit))rrrr�loggerrJrrrQrZdo_beginr �_reset_agentr>r?)r�transactionr@r$r$r%�_begin_impl�s








zConnection._begin_implc

Cs�|jr
t
�
|js|jjr$|j�|�

|jr�|jr>|jj�	d
�

zNy|jj
�|j�

Wn4t
k
r�
}

z|�|
dddd�
Wdd}
~
XYnXWd|js�|jj|jkr�d|j_d|_Xnd|_dS)NZROLLBACK)rrrrr�rollbackrIrr`rJrZdo_rollbackr r>r?rrar)rr@r$r$r%�_rollback_impl�s








(


zConnection._rollback_implc
Cs�|jr
t
�
|js|jjr$|j�|�

|jr8|jj�d
�

zNy|jj	�
|j�

Wn4tk
r�
}
z|�
|dddd�
Wdd}~XYnXWd|js�|jj|jkr�d|j_d|_XdS)NZCOMMIT)rrrrr�commitrr`rJrZ	do_commitr r>r?rrar)r�
autocommitr@r$r$r%�_commit_impl�s







(

zConnection._commit_implcCsd|jr
t
�
|js|jjr&|j�||
�
|
dkrF|jd
7_d|j}
|jr`|jj�	||
�
|
SdS)Nrzsa_savepoint_%s)
rrrrrZ	savepointrrIrZdo_savepoint)r�namer$r$r%�_savepoint_impls








zConnection._savepoint_implcCsH|jr
t
�
|js|jjr(|j�||
|�
|jr>|jj�||
�
||_	dS)
N)
rrrrrZrollback_savepointrIrZdo_rollback_to_savepointr)rri�contextr$r$r%�_rollback_to_savepoint_impls




z&Connection._rollback_to_savepoint_implcCsH|jr
t
�
|js|jjr(|j�||
|�
|jr>|jj�||
�
||_	dS)
N)
rrrrrZrelease_savepointrIrZdo_release_savepointr)rrirkr$r$r%�_release_savepoint_impls




z"Connection._release_savepoint_implcCsl|jr
t
�
|jr|jj�d
�

|js,|jjr<|j�||
j	�
|j
rh|jj�||
j	�
|j
jdkrh|
|j
_dS)NzBEGIN TWOPHASE (implicit))rrrrr`rJrrrWrVrIrZdo_begin_twophaser ra)rrbr$r$r%�_begin_twophase_impl%s






zConnection._begin_twophase_implcCsP|jr
t
�
|js|jjr&|j�||
�
|jrLt|jt	�s<t
�
|jj
�||
�
dS)
N)rrrrrZprepare_twophaserI�
isinstancerrXrZdo_prepare_twophase)rrVr$r$r%�_prepare_twophase_impl3s




z!Connection._prepare_twophase_implcCs�|jr
t
�
|js|jjr(|j�||
|�
|jrvt|jt	�s>t
�
z|jj
�||
|�
Wd|jj
|jkrld|j_
d|_Xnd|_dS)
N)rrrrrZrollback_twophaserIrorrXrr[r ra)rrV�is_preparedr$r$r%�_rollback_twophase_impl=s









z"Connection._rollback_twophase_implcCs�|jr
t
�
|js|jjr(|j�||
|�
|jrvt|jt	�s>t
�
z|jj
�||
|�
Wd|jj
|jkrld|j_
d|_Xnd|_dS)
N)rrrrrZcommit_twophaserIrorrXrr]r ra)rrVrqr$r$r%�_commit_twophase_implPs








z Connection._commit_twophase_implc

Cs|j�
�s|j��
dS)
N)r)r_re)
rr$r$r%�
_autorollbackas


zConnection._autorollbackc
Cs�|jr4z"y|`
Wntk
r$


YnXWd
d|_d
Sy
|j
}
Wntk
rR


Yn&X|
��
|
j|jkrnd
|
_|jsx|`
d|_d
|_d
S)a8Close this :class:`.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` referenced
        by the :class:`.Engine` that produced this
        :class:`.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:`.Connection`.

        After :meth:`~.Connection.close` is called, the
        :class:`.Connection` is permanently in a closed state,
        and will allow no further operations.

        NF)rrr<rr1rarr)r�connr$r$r%r1es$















zConnection.closecOs|j|
f
|�|�
�
�S)
z�Executes and returns the first column of the first row.

        The underlying result/cursor is closed after execution.
        )�execute�scalar)r�object_�multiparams�paramsr$r$r%rw�szConnection.scalarcOsXt|
t
jd
�r|�|
||�Sy
|
j}Wntk
rF


t�|
�
�
YnX||||�SdS)a�Executes a SQL statement construct and returns a
        :class:`.ResultProxy`.

        :param object: The statement to be executed.  May be
         one of:

         * a plain string
         * any :class:`.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

        :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 <http://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.

        r
N)rorZstring_types�
_execute_textZ_execute_on_connectionr<rZObjectNotExecutableError)rrxryrzZmethr$r$r%rv�s;





zConnection.executecCs|�|
�
�||�S)
z%Execute a sql.FunctionElement object.)�_execute_clauseelementZselect)r�funcryrzr$r$r%�_execute_function�szConnection._execute_functionc

Cs�|js|j
jr4x$|jjD]}|||
||�\}
}}qWyNy
|j}Wntk
rX


d
}YnX|d
krj|��}|j}|j�	|||�}Wn4t
k
r�
}
z|�|d
d
d
d
�
Wd
d
}~XYnX|�d
|
d
�}	|j
r�|��
|js�|j
jr�|j�||
|||	�
|	S)z&Execute a schema.ColumnDefault object.N)rrr�before_executerr<r=r�execution_ctx_clsZ
_init_defaultr>r?Z
_exec_defaultrr1�
after_execute)
r�defaultryrz�fnrur�ctxr@�retr$r$r%�_execute_default�s,












$



zConnection._execute_defaultcCs�|js|j
jr4x$|jjD]}|||
||�\}
}}qW|j}|
j||jjsN|jnd
d�}|�||j	j
|d
|�}|jsz|j
jr�|j�||
|||�
|S)zExecute a schema.DDL object.N)r�schema_translate_map)rrrrr�compiler�
is_default�_execute_contextr�Z	_init_ddlr�)rZddlryrzr�r�compiledr�r$r$r%�_execute_ddls"










zConnection._execute_ddlcCsD
|js|j
jr4x$|jjD]}|||
||�\}
}}qWt||�}|rTt|d
���
}ng}|j}d|jkr�||
t	t
|�
�
|jjt
|�
dkf}|jd�|�
}	|	dkr�|
j||t
|�
dk|jjs�|jndd�}	|	|jd|<n(|
j||t
|�
dk|jjs�|jndd�}	|�||jj|	||	|�}
|j�
s,|j
j�
r@|j�||
|||
�
|
S)z#Execute a sql.ClauseElement object.r
Zcompiled_cacherN)rZcolumn_keysZinliner�)rrrrr�list�keysrr�tuple�sortedrZhash_key�len�getr�r�r�r��_init_compiledr�)r�elemryrzr�Zdistilled_paramsr�r�keyZcompiled_sqlr�r$r$r%r| sN






























z!Connection._execute_clauseelementcCs�|js|j
jr4x$|jjD]}|||
||�\}
}}qW|j}t||�}|�||jj|
||
|�}|jsj|j
jr~|j�	||
|||�
|S)
zExecute a sql.Compiled object.)
rrrrrrr�r�r�r�)rr�ryrzr�r�
parametersr�r$r$r%�_execute_compiledYs"













zConnection._execute_compiledcCs�|js|j
jr4x$|jjD]}|||
||�\}
}}qW|j}t||�}|�||jj|
||
|�}|jsj|j
jr~|j�	||
|||�
|S)
zExecute a string SQL statement.)
rrrrrrr�r�Z_init_statementr�)r�	statementryrzr�rr�r�r$r$r%r{rs"













zConnection._execute_textc

GsyJy
|j}Wnt
k
r$


d
}YnX|d
kr6|��}||
||f|��}Wn:tk
r�
}
z|�|t�|�
|d
d
�
Wd
d
}~XYnX|jr�|��
|j	|j
|j}	}}|js�|d}|j
s�|jj
r�x(|jjD]}
|
||	||||j�\}}q�W|j�
r |jj�|�

|jj�dtj|dd��
d}�
y|j�
r�|jj
�
rfx*|jjjD]}
|
|	|||��
rFd}P�
qFW|�s(|j�|	|||�
n�|�
s�|j�
r�|jj
�
r�x(|jjjD]}
|
|	||��
r�d}P�
q�W|�s(|j�|	||�
nN|jj
�rx*|jjjD]}
|
|	|||��
r�d}P�
q�W|�s(|j�|	|||�
Wn6tk
�r`
}
z|�||||	|�
Wd
d
}~XYnX|j
�st|jj
�r�|j�||	||||j�
|j�r�|��
|j�s�|j�r�|��}n|� �}|j!d
k�r�|�"�
|j#�r�|j$j%d
k�r�|j$j&dd�

|j'�r|j(�r|�)�
nd|_*|S)	z\Create an :class:`.ExecutionContext` and execute, returning
        a :class:`.ResultProxy`.Nr
z%r�
)
ZbatchesFT)
rg)+rr<r=r>r?rZ	text_typer�Zpre_exec�cursorr�r�Zexecutemanyrrr�before_cursor_executerr`rJ�sql_utilZ_repr_paramsrZdo_executemanyZ
no_parametersZdo_execute_no_params�
do_execute�after_cursor_executeZ	post_execZis_crudZis_textZ_setup_crud_result_proxyZget_result_proxyZ	_metadataZ_soft_closeZshould_autocommitr)rrhrZ_soft_closedr1Z_autoclose_connection)
rr�constructorr�r��argsrurkr@r�r�Zevt_handled�resultr$r$r%r��s�









&












































 















zConnection._execute_contextc
Cs�|js|j
jr6x&|jjD]}|||
|||d
�\}}qW|jrZ|j
j�|�

|j
j�d|�
yFx@|jjsjdn|jjjD]}||
|||�rtPqtW|j�|
|||�
Wn4t	k
r�
}
z|�
||||
|�
Wdd}~XYnX|js�|j
jr�|j�||
|||d
�
dS)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%rr$N)rrrr�rr`rJrr�r>r?r�)rr�r�r�rkr�r@r$r$r%�_cursor_executes(











 

zConnection._cursor_executecCs:y|
��
Wn(t
k
r4


|jjjjd
dd�
YnXdS)z\Close the given cursor, catching exceptions
        and turning into log warnings.

        zError closing cursorT)
�exc_infoN)r1�	Exceptionr�poolr`�error)rr�r$r$r%�_safe_close_cursor/s




zConnection._safe_close_cursorcCs�t�
�}|r|jdkr|
|_t|
t�}|js|t|
|jjj�rb|j	rb|j�
|
|jsZ|jnd|�pl|ol|j	|_|r||j|_
|}|j
r�t�tjj|||
|jjj|jd
�|�
d|_
�
z�t|
|jjj�p�|dk	o�|dko�|}	|	�
rtjj|||
|jjj|j|jd�}
nd}
d}|j�
s"|jj�
r�|j�dd��
s�|	�
rT|�
rT|j�||||||
�
t|
|
|j||||||j|�
}x^|jjD]R}
y |
|�
}|dk	�
r�||_}Wn*tk
�
r�
}
z
|}PWdd}~XYnX�
q|W|j|j
k�
r�|j
|_|
�
r�|j
|
_|j}|	�r|�r|�|
�

|j�sJ|�r*|�|�

tj dd�
�
|�!�
WdQRX|�r^t�||�
n|	�rrt�|
|�
n
tj"|�
Wd|`
|j�r�|`|j�s�|j}|�r�|jj#�$||
�
|�%|
�

|j&�r�|�'�
XdS)N)
rT)�connection_invalidatedrZskip_user_error_eventsF)
Z	warn_only)(�sysr�rOror��_is_disconnectr�dbapi�Errorr:�
is_disconnectr;r�_reentrant_errorr�raise_from_causer�
DBAPIError�instancerrrr�rZdbapi_error�ExceptionContextImpl�handle_error�chained_exceptionr��invalidate_pool_on_disconnectZhandle_dbapi_exceptionr��safe_reraisert�reraiser�Z_invalidaterNrr1)rr@r�r�r�rkr�Zis_exit_exceptionr��should_wrap�sqlalchemy_exception�newraiser�r��per_fn�_raisedZdbapi_conn_wrapperr$r$r%r??s�



































































z"Connection._handle_dbapi_exceptionc
Cs
t�
�}|�|
dd�}t|
|jj�}|rDtjjdd|
|jj|d
�}nd}d}|j	r�t
|
||ddddd|d�
}	xX|jjD]L}
y|
|	�
}|dk	r�||	_
}Wqvtk
r�
}
z
|}PWdd}~XYqvXqvW|r�||	jkr�|	j|_}|r�t�||�
n|�
rt�||�
n
tj|�
dS)N)
r�T)r�r�r�ror�r�rr�r�rr�rr�r�r�r�rr�r�)
�clsr@rrr�r�r�r�r�r�r�r�r�r$r$r%�$_handle_dbapi_exception_noconnection�sN

























z/Connection._handle_dbapi_exception_noconnectioncOsT|��}y|j
|
f
|�|�
}|��
|S


t���
|��
Wd
QRXYnXd
S)a8Execute the given function within a transaction boundary.

        The function is passed this :class:`.Connection`
        as the first argument, followed by the given \*args and \**kwargs,
        e.g.::

            def do_something(conn, x, y):
                conn.execute("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:`.Connection.begin`::

               with conn.begin():
                   conn.execute("some statement", {'x':5, 'y':10})

           As well as with :meth:`.Engine.begin`::

               with engine.begin() as conn:
                   conn.execute("some statement", {'x':5, 'y':10})

        .. seealso::

            :meth:`.Engine.begin` - engine-level transactional
            context

            :meth:`.Engine.transaction` - engine-level version of
            :meth:`.Connection.transaction`

        N)rQ�run_callablerfrr�rd)r�	callable_r�rL�transr�r$r$r%rbs*







zConnection.transactioncOs|
|f
|�|�
S)
a�
Given a callable object or function, execute it, passing
        a :class:`.Connection` as the first argument.

        The given \*args and \**kwargs are passed subsequent
        to the :class:`.Connection` argument.

        This function, along with :meth:`.Engine.run_callable`,
        allows a function to be run with a :class:`.Connection`
        or :class:`.Engine` object without the need to know
        which one is being dealt with.

        r$)rr�r�rLr$r$r%r�7s
zConnection.run_callablecKs|
|j|f|�
�
|�

dS)
N)rZtraverse_single)r�visitorcallable�elementrLr$r$r%�_run_visitorFs
zConnection._run_visitor)NFNNNN)
N)
N)
F)
F)
F)
N)
N)C�__name__�
__module__�__qualname__�__doc__r�_schema_getterrr&r'�propertyr)r/r0r5r8r9r:r;r rArBr=rHrIrJrKrMrNrPrQrTrWrYr\r^r_rcrerhrjrlrmrnrprrrsrtr1rwrvr~r�r�r|r�r{r�r�r�r�r�r?�classmethodr�rbr�r�r$r$r$r%r
s�






2"	$
2,
!







-D#9|
(

:3r
c@seZ
dZd
Zdd�ZdS)r�z3Implement the :class:`.ExceptionContext` interface.cCs:||_||_
||_|
|_||_||_||_|	|_|
|_dS)
N)	rr r�Zoriginal_exceptionZexecution_contextr�r�r�r�)rrOr�rr r�r�r�rkr�r�r$r$r%r&Ms








zExceptionContextImpl.__init__N)r�r�r�r�r&r$r$r$r%r�Js
r�c@s\eZ
dZd
Zdd�Zedd��
Zdd�Zdd	�Zd
d�Z	dd
�Z
dd�Zdd�Zdd�Z
dS)rSa?Represent a database transaction in progress.

    The :class:`.Transaction` object is procured by
    calling the :meth:`~.Connection.begin` method of
    :class:`.Connection`::

        from sqlalchemy import create_engine
        engine = create_engine("postgresql://scott:tiger@localhost/test")
        connection = engine.connect()
        trans = connection.begin()
        connection.execute("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:`.Connection.begin` method::

        with connection.begin():
            connection.execute("insert into x (a, b) values (1, 2)")

    The Transaction object is **not** threadsafe.

    .. seealso::

        :meth:`.Connection.begin`

        :meth:`.Connection.begin_twophase`

        :meth:`.Connection.begin_nested`

    .. index::
      single: thread safety; Transaction
    cCs|
|_||_
d
|_dS)NT)r �_actual_parent�	is_active)rr �parentr$r$r%r&�s


zTransaction.__init__c


Cs
|jp|S)
N)
r�)
rr$r$r%�_parent�szTransaction._parentc

Cs"|jj
sd
S|j|kr|��
d
S)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)r�r�rd)
rr$r$r%r1�s



zTransaction.closec

Cs|jj
sd
S|��
d|_
d
S)z/Roll back this :class:`.Transaction`.

        NF)r�r��_do_rollback)
rr$r$r%rd�s


zTransaction.rollbackc

Cs|j�
�
dS)
N)r�rd)
rr$r$r%r��s
zTransaction._do_rollbackc

Cs$|jj
st�d
�
�
|��
d|_
dS)z"Commit this :class:`.Transaction`.zThis transaction is inactiveFN)r�r�rrD�
_do_commit)
rr$r$r%rf�s



zTransaction.commitc


CsdS)
Nr$)
rr$r$r%r��s
zTransaction._do_commitc


Cs|S)
Nr$)
rr$r$r%r0�s
zTransaction.__enter__cCsR|
dkrF|jrFy|�
�
WqN


t���
|��
WdQRXYqNXn|��
dS)
N)r�rfrr�rd)rr2r3r4r$r$r%r5�s






zTransaction.__exit__N)r�r�r�r�r&r�r�r1rdr�rfr�r0r5r$r$r$r%rSes#	rScs,eZ
dZ�f
d
d�Zdd�Zdd�Z�ZS)rRcs"tt
|��|
d�
|j�|�

dS)
N)�superrRr&r rc)rr )
r*r$r%r&�s

zRootTransaction.__init__c

Cs|jr|j
��
dS)
N)r�r re)
rr$r$r%r��s

zRootTransaction._do_rollbackc

Cs|jr|j
��
dS)
N)r�r rh)
rr$r$r%r��s

zRootTransaction._do_commit)r�r�r�r&r�r��
__classcell__r$r$)
r*r%rR�s
rRcs0eZ
dZd
Z�f
dd�Zdd�Zdd�Z�ZS)rUz�Represent a 'nested', or SAVEPOINT transaction.

    A new :class:`.NestedTransaction` object may be procured
    using the :meth:`.Connection.begin_nested` method.

    The interface is the same as that of :class:`.Transaction`.

    cs"tt
|��|
|�
|j��|_dS)
N)r�rUr&r rj�
_savepoint)rr r�)
r*r$r%r&�s

zNestedTransaction.__init__c

Cs|jr|j
�|j|j�
dS)
N)r�r rlr�r�)
rr$r$r%r��s


zNestedTransaction._do_rollbackc

Cs|jr|j
�|j|j�
dS)
N)r�r rmr�r�)
rr$r$r%r��s


zNestedTransaction._do_commit)r�r�r�r�r&r�r�r�r$r$)
r*r%rU�srUcs8eZ
dZd
Z�f
dd�Zdd�Zdd�Zdd	�Z�ZS)
rXa
Represent a two-phase transaction.

    A new :class:`.TwoPhaseTransaction` object may be procured
    using the :meth:`.Connection.begin_twophase` method.

    The interface is the same as that of :class:`.Transaction`
    with the addition of the :meth:`prepare` method.

    cs.tt
|��|
d�
d
|_||_|j�|�

dS)NF)r�rXr&�_is_preparedrVr rn)rr rV)
r*r$r%r&�s



zTwoPhaseTransaction.__init__c

Cs*|jj
st�d
�
�
|j�|j�

d|_dS)zqPrepare this :class:`.TwoPhaseTransaction`.

        After a PREPARE, the transaction can be committed.

        zThis transaction is inactiveTN)r�r�rrDr rprVr�)
rr$r$r%�prepares



zTwoPhaseTransaction.preparec

Cs|j�
|j|j�
dS)
N)r rrrVr�)
rr$r$r%r�
s
z TwoPhaseTransaction._do_rollbackc

Cs|j�
|j|j�
dS)
N)r rsrVr�)
rr$r$r%r�s
zTwoPhaseTransaction._do_commit)	r�r�r�r�r&r�r�r�r�r$r$)
r*r%rX�s
	rXc@sD
eZ
dZd
Ze��ZdZeZ	e
�d�
Zd<dd�
Z
edd��
Zdd	�Zd
d�Zdd
�Zedd��
Zedd��
Ze��Zdd�Zdd�Zdd�Zejd=dd�
�
Zd>dd�
ZGdd�de�Z d?dd�
Z!d d!�Z"d"d#�Z#d$d%�Z$d&d'�Z%d@d(d)�
Z&d*d+�Z'd,d-�Z(e�)d.d/�dAd0d1�
�
Z*dBd2d3�
Z+dCd4d5�
Z,dDd6d7�
Z-d8d9�Z.dEd:d;�
Z/dS)F�Enginea{

    Connects a :class:`~sqlalchemy.pool.Pool` and
    :class:`~sqlalchemy.engine.interfaces.Dialect` together to provide a
    source of database connectivity and behavior.

    An :class:`.Engine` object is instantiated publicly using the
    :func:`~sqlalchemy.create_engine` function.

    .. seealso::

        :doc:`/core/engines`

        :ref:`connections_toplevel`

    FNcCsV|
|_||_
||_|r||_||_tj||d
�
|rBtj�	||�
|rR|j
f|�

dS)N)
�echoflag)r��urlr�logging_name�echor
�instance_loggerr	ZConnectionProxyZ_adapt_listener�update_execution_options)rr�rr�r�r��proxyr8r$r$r%r&9s










zEngine.__init__c


Cs|S)
Nr$)
rr$r$r%rOsz
Engine.enginec
Ks.|j�
|
�
|_|j�||
�
|j�||
�
d
S)a�
Update the default execution_options dictionary
        of this :class:`.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:`.create_engine`.

        .. seealso::

            :meth:`.Connection.execution_options`

            :meth:`.Engine.execution_options`

        N)rr6rZset_engine_execution_optionsr)rr7r$r$r%r�Ss

zEngine.update_execution_optionsc
Ks
t||
�S)
a�Return a new :class:`.Engine` that will provide
        :class:`.Connection` objects with the given execution options.

        The returned :class:`.Engine` remains related to the original
        :class:`.Engine` in that it shares the same connection pool and
        other state:

        * The :class:`.Pool` used by the new :class:`.Engine` is the
          same instance.  The :meth:`.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`
          inherits the events of the parent, and new events can be associated
          with the new :class:`.Engine` individually.
        * The logging configuration and logging_name is copied from the parent
          :class:`.Engine`.

        The intent of the :meth:`.Engine.execution_options` method is
        to implement "sharding" schemes where multiple :class:`.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:`.Connection` objects that will contain the execution option
        ``shard_id=shard1``, and ``shard2`` will produce :class:`.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:`.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:`.Connection.execution_options` - update execution options
            on a :class:`.Connection` object.

            :meth:`.Engine.update_execution_options` - update the execution
            options for a given :class:`.Engine` in place.

            :meth:`.Engine.get_execution_options`


        )
�OptionEngine)rr7r$r$r%r8hsBzEngine.execution_optionsc


Cs|jS)
z� Get the non-SQL options which will take effect during execution.

        .. versionadded: 1.3

        .. seealso::

            :meth:`.Engine.execution_options`
        )
r)
rr$r$r%r9�s	zEngine.get_execution_optionsc


Cs|jj
S)
ziString name of the :class:`~sqlalchemy.engine.interfaces.Dialect`
        in use by this :class:`Engine`.)rri)
rr$r$r%ri�szEngine.namec


Cs|jj
S)
ziDriver name of the :class:`~sqlalchemy.engine.interfaces.Dialect`
        in use by this :class:`Engine`.)r�driver)
rr$r$r%r��sz
Engine.driverc

Cs
d
|jS)Nz
Engine(%r))
r�)
rr$r$r%�__repr__�s
zEngine.__repr__c

Cs&|j�
�
|j��|_|j�|�

d
S)a�Dispose of the connection pool used by this :class:`.Engine`.

        This 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`, so when they are closed individually,
        eventually the :class:`.Pool` which they are associated with will
        be garbage collected and they will be closed out fully, if
        not already closed on checkin.

        A new connection pool is created immediately after the old one has
        been disposed.   This new pool, like all SQLAlchemy connection pools,
        does not make any actual connections to the database until one is
        first requested, so as long as the :class:`.Engine` isn't used again,
        no new connections will be made.

        .. seealso::

            :ref:`engine_disposal`

        N)r��disposeZrecreaterZengine_disposed)
rr$r$r%r��s


zEngine.disposec	Cs"|���}|�
|
d
i�SQRXdS)Nr$)rMr�)rr�rur$r$r%r��s


zEngine._execute_defaultc	cs.|
dkr$|���}|V
WdQRXn|
V
dS)
N)
rM)rr rur$r$r%�_optional_conn_ctx_manager�s


z!Engine._optional_conn_ctx_managerc	Ks*|�|�
�}|j
|
|f|�

WdQRXdS)
N)r�r�)rr�r�r rLrur$r$r%r��s
zEngine._run_visitorc@s$eZ
dZd
d�Zdd�Zdd�ZdS)zEngine._trans_ctxcCs|
|_||_
||_dS)
N)rurbr!)rrurbr!r$r$r%r&�s


zEngine._trans_ctx.__init__c


Cs|jS)
N)
ru)
rr$r$r%r0�s
zEngine._trans_ctx.__enter__cCs2|
dk	r|j�
�
n
|j��
|js.|j��
dS)
N)rbrdrfr!rur1)rr2r3r4r$r$r%r5�s





zEngine._trans_ctx.__exit__N)r�r�r�r&r0r5r$r$r$r%�
_trans_ctx�s
r�cCsP|j|
d
�
}y|�
�}Wn(


t���
|��
WdQRXYnXt�|||
�S)a�Return a context manager delivering a :class:`.Connection`
        with a :class:`.Transaction` established.

        E.g.::

            with engine.begin() as conn:
                conn.execute("insert into table (x, y, z) values (1, 2, 3)")
                conn.execute("my_special_procedure(5)")

        Upon successful operation, the :class:`.Transaction`
        is committed.  If an error is raised, the :class:`.Transaction`
        is rolled back.

        The ``close_with_result`` flag is normally ``False``, and indicates
        that the :class:`.Connection` will be closed when the operation
        is complete.   When set to ``True``, it indicates the
        :class:`.Connection` is in "single use" mode, where the
        :class:`.ResultProxy` returned by the first call to
        :meth:`.Connection.execute` will close the :class:`.Connection` when
        that :class:`.ResultProxy` has exhausted all result rows.

        .. seealso::

            :meth:`.Engine.connect` - procure a :class:`.Connection` from
            an :class:`.Engine`.

            :meth:`.Connection.begin` - start a :class:`.Transaction`
            for a particular :class:`.Connection`.

        )
r!N)rMrQrr�r1r�r�)rr!rur�r$r$r%rQs






zEngine.beginc	Os&|���}|j
|
f
|�|�
SQRXd
S)a�Execute the given function within a transaction boundary.

        The function is passed a :class:`.Connection` newly procured
        from :meth:`.Engine.contextual_connect` as the first argument,
        followed by the given \*args and \**kwargs.

        e.g.::

            def do_something(conn, x, y):
                conn.execute("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.begin`::

               with engine.begin() as conn:
                   conn.execute("some statement", {'x':5, 'y':10})

        .. seealso::

            :meth:`.Engine.begin` - engine-level transactional
            context

            :meth:`.Connection.transaction` - connection-level version of
            :meth:`.Engine.transaction`

        N)rMrb)rr�r�rLrur$r$r%rb.s'

zEngine.transactionc	Os&|���}|j
|
f
|�|�
SQRXd
S)a�
Given a callable object or function, execute it, passing
        a :class:`.Connection` as the first argument.

        The given \*args and \**kwargs are passed subsequent
        to the :class:`.Connection` argument.

        This function, along with :meth:`.Connection.run_callable`,
        allows a function to be run with a :class:`.Connection`
        or :class:`.Engine` object without the need to know
        which one is being dealt with.

        N)rMr�)rr�r�rLrur$r$r%r�Xs

zEngine.run_callablecOs|jd
d�
}|j
|
f
|�|�
S)a�Executes the given construct and returns a :class:`.ResultProxy`.

        The arguments are the same as those used by
        :meth:`.Connection.execute`.

        Here, a :class:`.Connection` is acquired using the
        :meth:`~.Engine.contextual_connect` method, and the statement executed
        with that connection. The returned :class:`.ResultProxy` is flagged
        such that when the :class:`.ResultProxy` is exhausted and its
        underlying cursor is closed, the :class:`.Connection` created here
        will also be closed, which allows its associated DBAPI connection
        resource to be returned to the connection pool.

        T)
r!)rMrv)rr�ryrzr r$r$r%rvhs
zEngine.executecOs|j|
f
|�|�
�
�S)
N)rvrw)rr�ryrzr$r$r%rw{s
z
Engine.scalarcCs|jd
d�
}|�
|
||�S)NT)
r!)rMr|)rr�ryrzr r$r$r%r|~s

zEngine._execute_clauseelementcCs|jd
d�
}|�
|
||�S)NT)
r!)rMr�)rr�ryrzr r$r$r%r��s

zEngine._execute_compiledc
Ks|j|f
|
�
S)
aOReturn a new :class:`.Connection` object.

        The :class:`.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`
        referenced by this :class:`.Engine`. When the
        :meth:`~.Connection.close` method of the :class:`.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.connect`.

        )
r()rrLr$r$r%rK�szEngine.connectz1.3z�The :meth:`.Engine.contextual_connect` method is deprecated.  This method is an artifact of the threadlocal engine strategy which is also to be deprecated.   For explicit connections from an :class:`.Engine`, use the :meth:`.Engine.connect` method.cKs|jfd
|
i
|��
S)a�Return a :class:`.Connection` object which may be part of some
        ongoing context.

        By default, this method does the same thing as :meth:`.Engine.connect`.
        Subclasses of :class:`.Engine` may override this method
        to provide contextual behavior.

        :param close_with_result: When True, the first :class:`.ResultProxy`
          created by the :class:`.Connection` will call the
          :meth:`.Connection.close` method of that connection as soon as any
          pending result rows are exhausted. This is used to supply the
          "connectionless execution" behavior provided by the
          :meth:`.Engine.execute` method.

        r!)
rM)rr!rLr$r$r%�contextual_connect�s
zEngine.contextual_connectcKs$|j||�
|jjd�fd
|
i
|��
S)Nr!)r(�_wrap_pool_connectr�rK)rr!rLr$r$r%rM�s





zEngine._contextual_connectc	Cs0|�|�
�}|
s|j
j}
|j
�||
�SQRXd
S)a
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. Default is
          the ``contextual_connect`` for this ``Engine``.
        N)r�rZdefault_schema_nameZget_table_names)rrr rur$r$r%�table_names�s	


zEngine.table_namescCs|�|j
j|
|�S)
aU
Return True if the given backend has a table of the given name.

        .. seealso::

            :ref:`metadata_reflection_inspector` - detailed schema inspection
            using the :class:`.Inspector` interface.

            :class:`.quoted_name` - used to pass quoting information along
            with a schema identifier.

        )r�r�	has_table)rZ
table_namerr$r$r%r��szEngine.has_tablec
Cs^|j}y|
�S|j
jk
rX
}
z*|dkr:t�|||�
ntjt���
Wdd}~XYnXdS)
N)	rr�r�r
r�rr�r�r�)rr�r rr@r$r$r%r��s






zEngine._wrap_pool_connectcCs|�|j
j|
�S)
a&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:`.Connection`
        is not needed.   When a :class:`.Connection` object is already
        present, the DBAPI connection is available using
        the :attr:`.Connection.connection` accessor.

        .. seealso::

            :ref:`dbapi_connections`

        )r�r�Zunique_connection)rrCr$r$r%r�s
zEngine.raw_connection)NNNN)
N)
N)
F)NN)
F)
F)NN)
N)
N)0r�r�r�r�rZ
immutabledictrrr
r(rr�rr&r�rr�r8r9rir�r
Z
echo_propertyr�r�r�r��
contextlib�contextmanagerr�r��objectr�rQrbr�rvrwr|r�rKZ
deprecatedr�rMr�r�r�rr$r$r$r%r�sP






D


'*





r�c@sLeZ
dZd
Zdd�Zdd�Zdd�Zeee�Zdd	�Z	d
d�Z
ee	e
�ZdS)
r�FcCs^|
|_|
j
|_
|
j|_|
j|_|
j|_tj||jd
�
|j�|
j�
|_|
j	|_	|j
f|�

dS)N)
r�)�_proxiedr�rr�r�r
r�rrrr�)rZproxiedr8r$r$r%r&�s






zOptionEngine.__init__c


Cs|jj
S)
N)r�r�)
rr$r$r%�	_get_pool	s
zOptionEngine._get_poolcCs|
|j_
dS)
N)r�r�)rr�r$r$r%�	_set_pool	s
zOptionEngine._set_poolc

Cs|jj
p|j�d
d�S)NrF)r�rr,r�)
rr$r$r%�_get_has_events 	s

zOptionEngine._get_has_eventscCs|
|jd
<dS)Nr)
r,)rr3r$r$r%�_set_has_events%	s
zOptionEngine._set_has_eventsN)r�r�r�Z_sa_propagate_class_eventsr&r�r�r�r�r�r�rr$r$r$r%r��s

r�)Z
__future__rr�r�r	rrrr�rr
Zsqlrr�r
r�r�rSrRrUrXZ
Identifiedr�r�r$r$r$r%�<module>sD








:c#k