\H7AZ $ d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z d d
l
m Z d d l
mZ G d d
e Z G d de Z G d de Z G d de Z G d de Z G d dee ZeZdS )a>
.. dialect:: mssql+mxodbc
:name: mxODBC
:dbapi: mxodbc
:connectstring: mssql+mxodbc://:@
:url: http://www.egenix.com/
Execution Modes
---------------
mxODBC features two styles of statement execution, using the
``cursor.execute()`` and ``cursor.executedirect()`` methods (the second being
an extension to the DBAPI specification). The former makes use of a particular
API call specific to the SQL Server Native Client ODBC driver known
SQLDescribeParam, while the latter does not.
mxODBC apparently only makes repeated use of a single prepared statement
when SQLDescribeParam is used. The advantage to prepared statement reuse is
one of performance. The disadvantage is that SQLDescribeParam has a limited
set of scenarios in which bind parameters are understood, including that they
cannot be placed within the argument lists of function calls, anywhere outside
the FROM, or even within subqueries within the FROM clause - making the usage
of bind parameters within SELECT statements impossible for all but the most
simplistic statements.
For this reason, the mxODBC dialect uses the "native" mode by default only for
INSERT, UPDATE, and DELETE statements, and uses the escaped string mode for
all other statements.
This behavior can be controlled via
:meth:`~sqlalchemy.sql.expression.Executable.execution_options` using the
``native_odbc_execute`` flag with a value of ``True`` or ``False``, where a
value of ``True`` will unconditionally use native bind parameters and a value
of ``False`` will unconditionally use string-escaped parameters.
)_MSDate) _MSDateTime)_MSTime) MSDialect) VARBINARY)_MSNumeric_pyodbc)MSExecutionContext_pyodbc )types)MxODBCConnectorc e Zd ZdZdS )_MSNumeric_mxodbcz#Include pyodbc's numeric processor.N__name__
__module__ __qualname____doc__ t/builddir/build/BUILD/cloudlinux-venv-1.0.10/venv/lib64/python3.11/site-packages/sqlalchemy/dialects/mssql/mxodbc.pyr r 9 s ----r r c e Zd Zd ZdS )_MSDate_mxodbcc d }|S )Nc < | | j d| j d| j S d S )N-)yearmonthdayvalues r processz._MSDate_mxodbc.bind_processor..process? s* %*ZZZeiiHHtr r selfdialectr! s r bind_processorz _MSDate_mxodbc.bind_processor> r Nr r r r% r r r r r = # r r c e Zd Zd ZdS )_MSTime_mxodbcc d }|S )Nc < | | j d| j d| j S d S )N:)hourminutesecondr s r r! z._MSTime_mxodbc.bind_processor..processJ s* %*ZZZ u||LLtr r r" s r r% z _MSTime_mxodbc.bind_processorI r& r Nr' r r r r* r* H r( r r* c e Zd ZdZd ZdS )_VARBINARY_mxodbcz
mxODBC Support for VARBINARY column types.
This handles the special case for null VARBINARY values,
which maps None values to the mx.ODBC.Manager.BinaryNull symbol.
c @ j d S j j fd}|S )Nc 6 | | S j j S N)dbapi
BinaryNull)r DBAPIBinaryr$ s r r! z1_VARBINARY_mxodbc.bind_processor..processb s& "{5))) }//r )r6 Binary)r# r$ r! r8 s ` @r r% z _VARBINARY_mxodbc.bind_processor\ s@ = 4 m* 0 0 0 0 0 0 r N)r r r r r% r r r r2 r2 S s-
r r2 c e Zd ZdZdS )MSExecutionContext_mxodbcz
The pyodbc execution context is useful for enabling
SELECT SCOPE_IDENTITY in cases where OUTPUT clause
does not work (tables with insert triggers).
Nr r r r r; r; l s r r; c v e Zd ZeZdZej eej e
ej e ej
eeeej eiZd fd Z xZS )MSDialect_mxodbcTNc V t t | j di | || _ d S )Nr )superr= __init__description_encoding)r# rA params __class__s r r@ zMSDialect_mxodbc.__init__ s5 . %%.88888$8!!!r r5 )r r r r; execution_ctx_cls_need_decimal_fixsqltypesNumericr DateTimer Dater Timer* r r2 LargeBinarycolspecsr@
__classcell__)rC s @r r= r= x s 2 +;
~
~$ /
H9 9 9 9 9 9 9 9 9 9r r= N)r baser r r r r pyodbcr r r rF connectors.mxodbcr r r r* r2 r; r= r$ r r r rR s # #L % % % % % % - - - - - - ! ! ! ! ! ! 0 0 0 0 0 0. . . . .) . . . W W 2 9 9 9 9 9 9 9 9 92 r