w G d; de?ej@ ZA G d? d@e?ejB ZC G dA dBejD ZE G dC dDeE ZF G dE dFejB ZG G dG dHejH ejI ZH G dI dJejI ZJ G dK dLejK ZL G dM dNej= ZM G dO dPej= ZN G dQ dRej= ZO G dS dTej= ZP G dU dVej= ZQ G dW dXe jR jS ZT e'eTdY ZUe:ZVe4ZWe0ZXe2ZYe5ZZe;Z[eZ]e#Z^eGZ_e$Z`e!ZaeZbe ZceZdeHZeeJZfeMZgeNZheOZiePZjeQZki dZe d[ed\e"d]e2d^e$d_e!d`edae dbe#dceGdde dee dfe dgedhe<die>djee5e;eeHeMe0eJeLeEeNeOePeQdk
Zl G dl dmejm Zn G dn doejo Zp G dp dqejq Zr G dr dser Zs G dt duejt Zu G dv dwejv Zwdx Zxdy Zydz Zzd{ Z{ ej| Z}d| Z~ G d} d~ej ZdS )a![
.. dialect:: mssql
:name: Microsoft SQL Server
.. _mssql_external_dialects:
External Dialects
-----------------
In addition to the above DBAPI layers with native SQLAlchemy support, there
are third-party dialects for other DBAPI layers that are compatible
with SQL Server. See the "External Dialects" list on the
:ref:`dialect_toplevel` page.
.. _mssql_identity:
Auto Increment Behavior / IDENTITY Columns
------------------------------------------
SQL Server provides so-called "auto incrementing" behavior using the
``IDENTITY`` construct, which can be placed on any single integer column in a
table. SQLAlchemy considers ``IDENTITY`` within its default "autoincrement"
behavior for an integer primary key column, described at
:paramref:`_schema.Column.autoincrement`. This means that by default,
the first
integer primary key column in a :class:`_schema.Table`
will be considered to be the
identity column and will generate DDL as such::
from sqlalchemy import Table, MetaData, Column, Integer
m = MetaData()
t = Table('t', m,
Column('id', Integer, primary_key=True),
Column('x', Integer))
m.create_all(engine)
The above example will generate DDL as:
.. sourcecode:: sql
CREATE TABLE t (
id INTEGER NOT NULL IDENTITY(1,1),
x INTEGER NULL,
PRIMARY KEY (id)
)
For the case where this default generation of ``IDENTITY`` is not desired,
specify ``False`` for the :paramref:`_schema.Column.autoincrement` flag,
on the first integer primary key column::
m = MetaData()
t = Table('t', m,
Column('id', Integer, primary_key=True, autoincrement=False),
Column('x', Integer))
m.create_all(engine)
To add the ``IDENTITY`` keyword to a non-primary key column, specify
``True`` for the :paramref:`_schema.Column.autoincrement` flag on the desired
:class:`_schema.Column` object, and ensure that
:paramref:`_schema.Column.autoincrement`
is set to ``False`` on any integer primary key column::
m = MetaData()
t = Table('t', m,
Column('id', Integer, primary_key=True, autoincrement=False),
Column('x', Integer, autoincrement=True))
m.create_all(engine)
.. versionchanged:: 1.3 Added ``mssql_identity_start`` and
``mssql_identity_increment`` parameters to :class:`_schema.Column`.
These replace
the use of the :class:`.Sequence` object in order to specify these values.
.. deprecated:: 1.3
The use of :class:`.Sequence` to specify IDENTITY characteristics is
deprecated and will be removed in a future release. Please use
the ``mssql_identity_start`` and ``mssql_identity_increment`` parameters
documented at :ref:`mssql_identity`.
.. note::
There can only be one IDENTITY column on the table. When using
``autoincrement=True`` to enable the IDENTITY keyword, SQLAlchemy does not
guard against multiple columns specifying the option simultaneously. The
SQL Server database will instead reject the ``CREATE TABLE`` statement.
.. note::
An INSERT statement which attempts to provide a value for a column that is
marked with IDENTITY will be rejected by SQL Server. In order for the
value to be accepted, a session-level option "SET IDENTITY_INSERT" must be
enabled. The SQLAlchemy SQL Server dialect will perform this operation
automatically when using a core :class:`_expression.Insert`
construct; if the
execution specifies a value for the IDENTITY column, the "IDENTITY_INSERT"
option will be enabled for the span of that statement's invocation.However,
this scenario is not high performing and should not be relied upon for
normal use. If a table doesn't actually require IDENTITY behavior in its
integer primary key column, the keyword should be disabled when creating
the table by ensuring that ``autoincrement=False`` is set.
Controlling "Start" and "Increment"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Specific control over the "start" and "increment" values for
the ``IDENTITY`` generator are provided using the
``mssql_identity_start`` and ``mssql_identity_increment`` parameters
passed to the :class:`_schema.Column` object::
from sqlalchemy import Table, Integer, Column
test = Table(
'test', metadata,
Column(
'id', Integer, primary_key=True, mssql_identity_start=100,
mssql_identity_increment=10
),
Column('name', String(20))
)
The CREATE TABLE for the above :class:`_schema.Table` object would be:
.. sourcecode:: sql
CREATE TABLE test (
id INTEGER NOT NULL IDENTITY(100,10) PRIMARY KEY,
name VARCHAR(20) NULL,
)
.. versionchanged:: 1.3 The ``mssql_identity_start`` and
``mssql_identity_increment`` parameters are now used to affect the
``IDENTITY`` generator for a :class:`_schema.Column` under SQL Server.
Previously, the :class:`.Sequence` object was used. As SQL Server now
supports real sequences as a separate construct, :class:`.Sequence` will be
functional in the normal way in a future SQLAlchemy version.
INSERT behavior
^^^^^^^^^^^^^^^^
Handling of the ``IDENTITY`` column at INSERT time involves two key
techniques. The most common is being able to fetch the "last inserted value"
for a given ``IDENTITY`` column, a process which SQLAlchemy performs
implicitly in many cases, most importantly within the ORM.
The process for fetching this value has several variants:
* In the vast majority of cases, RETURNING is used in conjunction with INSERT
statements on SQL Server in order to get newly generated primary key values:
.. sourcecode:: sql
INSERT INTO t (x) OUTPUT inserted.id VALUES (?)
* When RETURNING is not available or has been disabled via
``implicit_returning=False``, either the ``scope_identity()`` function or
the ``@@identity`` variable is used; behavior varies by backend:
* when using PyODBC, the phrase ``; select scope_identity()`` will be
appended to the end of the INSERT statement; a second result set will be
fetched in order to receive the value. Given a table as::
t = Table('t', m, Column('id', Integer, primary_key=True),
Column('x', Integer),
implicit_returning=False)
an INSERT will look like:
.. sourcecode:: sql
INSERT INTO t (x) VALUES (?); select scope_identity()
* Other dialects such as pymssql will call upon
``SELECT scope_identity() AS lastrowid`` subsequent to an INSERT
statement. If the flag ``use_scope_identity=False`` is passed to
:func:`_sa.create_engine`,
the statement ``SELECT @@identity AS lastrowid``
is used instead.
A table that contains an ``IDENTITY`` column will prohibit an INSERT statement
that refers to the identity column explicitly. The SQLAlchemy dialect will
detect when an INSERT construct, created using a core
:func:`_expression.insert`
construct (not a plain string SQL), refers to the identity column, and
in this case will emit ``SET IDENTITY_INSERT ON`` prior to the insert
statement proceeding, and ``SET IDENTITY_INSERT OFF`` subsequent to the
execution. Given this example::
m = MetaData()
t = Table('t', m, Column('id', Integer, primary_key=True),
Column('x', Integer))
m.create_all(engine)
with engine.begin() as conn:
conn.execute(t.insert(), {'id': 1, 'x':1}, {'id':2, 'x':2})
The above column will be created with IDENTITY, however the INSERT statement
we emit is specifying explicit values. In the echo output we can see
how SQLAlchemy handles this:
.. sourcecode:: sql
CREATE TABLE t (
id INTEGER NOT NULL IDENTITY(1,1),
x INTEGER NULL,
PRIMARY KEY (id)
)
COMMIT
SET IDENTITY_INSERT t ON
INSERT INTO t (id, x) VALUES (?, ?)
((1, 1), (2, 2))
SET IDENTITY_INSERT t OFF
COMMIT
This
is an auxiliary use case suitable for testing and bulk insert scenarios.
MAX on VARCHAR / NVARCHAR
-------------------------
SQL Server supports the special string "MAX" within the
:class:`_types.VARCHAR` and :class:`_types.NVARCHAR` datatypes,
to indicate "maximum length possible". The dialect currently handles this as
a length of "None" in the base type, rather than supplying a
dialect-specific version of these types, so that a base type
specified such as ``VARCHAR(None)`` can assume "unlengthed" behavior on
more than one backend without using dialect-specific types.
To build a SQL Server VARCHAR or NVARCHAR with MAX length, use None::
my_table = Table(
'my_table', metadata,
Column('my_data', VARCHAR(None)),
Column('my_n_data', NVARCHAR(None))
)
Collation Support
-----------------
Character collations are supported by the base string types,
specified by the string argument "collation"::
from sqlalchemy import VARCHAR
Column('login', VARCHAR(32, collation='Latin1_General_CI_AS'))
When such a column is associated with a :class:`_schema.Table`, the
CREATE TABLE statement for this column will yield::
login VARCHAR(32) COLLATE Latin1_General_CI_AS NULL
LIMIT/OFFSET Support
--------------------
MSSQL has no support for the LIMIT or OFFSET keywords. LIMIT is
supported directly through the ``TOP`` Transact SQL keyword::
select.limit
will yield::
SELECT TOP n
If using SQL Server 2005 or above, LIMIT with OFFSET
support is available through the ``ROW_NUMBER OVER`` construct.
For versions below 2005, LIMIT with OFFSET usage will fail.
.. _mssql_isolation_level:
Transaction Isolation Level
---------------------------
All SQL Server dialects support setting of transaction isolation level
both via a dialect-specific parameter
:paramref:`_sa.create_engine.isolation_level`
accepted by :func:`_sa.create_engine`,
as well as the :paramref:`.Connection.execution_options.isolation_level`
argument as passed to
:meth:`_engine.Connection.execution_options`.
This feature works by issuing the
command ``SET TRANSACTION ISOLATION LEVEL `` for
each new connection.
To set isolation level using :func:`_sa.create_engine`::
engine = create_engine(
"mssql+pyodbc://scott:tiger@ms_2008",
isolation_level="REPEATABLE READ"
)
To set using per-connection execution options::
connection = engine.connect()
connection = connection.execution_options(
isolation_level="READ COMMITTED"
)
Valid values for ``isolation_level`` include:
* ``AUTOCOMMIT`` - pyodbc / pymssql-specific
* ``READ COMMITTED``
* ``READ UNCOMMITTED``
* ``REPEATABLE READ``
* ``SERIALIZABLE``
* ``SNAPSHOT`` - specific to SQL Server
.. versionadded:: 1.2 added AUTOCOMMIT isolation level setting
.. seealso::
:ref:`dbapi_autocommit`
Nullability
-----------
MSSQL has support for three levels of column nullability. The default
nullability allows nulls and is explicit in the CREATE TABLE
construct::
name VARCHAR(20) NULL
If ``nullable=None`` is specified then no specification is made. In
other words the database's configured default is used. This will
render::
name VARCHAR(20)
If ``nullable`` is ``True`` or ``False`` then the column will be
``NULL`` or ``NOT NULL`` respectively.
Date / Time Handling
--------------------
DATE and TIME are supported. Bind parameters are converted
to datetime.datetime() objects as required by most MSSQL drivers,
and results are processed from strings if needed.
The DATE and TIME types are not available for MSSQL 2005 and
previous - if a server version below 2008 is detected, DDL
for these types will be issued as DATETIME.
.. _mssql_large_type_deprecation:
Large Text/Binary Type Deprecation
----------------------------------
Per
`SQL Server 2012/2014 Documentation `_,
the ``NTEXT``, ``TEXT`` and ``IMAGE`` datatypes are to be removed from SQL
Server in a future release. SQLAlchemy normally relates these types to the
:class:`.UnicodeText`, :class:`_expression.TextClause` and
:class:`.LargeBinary` datatypes.
In order to accommodate this change, a new flag ``deprecate_large_types``
is added to the dialect, which will be automatically set based on detection
of the server version in use, if not otherwise set by the user. The
behavior of this flag is as follows:
* When this flag is ``True``, the :class:`.UnicodeText`,
:class:`_expression.TextClause` and
:class:`.LargeBinary` datatypes, when used to render DDL, will render the
types ``NVARCHAR(max)``, ``VARCHAR(max)``, and ``VARBINARY(max)``,
respectively. This is a new behavior as of the addition of this flag.
* When this flag is ``False``, the :class:`.UnicodeText`,
:class:`_expression.TextClause` and
:class:`.LargeBinary` datatypes, when used to render DDL, will render the
types ``NTEXT``, ``TEXT``, and ``IMAGE``,
respectively. This is the long-standing behavior of these types.
* The flag begins with the value ``None``, before a database connection is
established. If the dialect is used to render DDL without the flag being
set, it is interpreted the same as ``False``.
* On first connection, the dialect detects if SQL Server version 2012 or
greater is in use; if the flag is still at ``None``, it sets it to ``True``
or ``False`` based on whether 2012 or greater is detected.
* The flag can be set to either ``True`` or ``False`` when the dialect
is created, typically via :func:`_sa.create_engine`::
eng = create_engine("mssql+pymssql://user:pass@host/db",
deprecate_large_types=True)
* Complete control over whether the "old" or "new" types are rendered is
available in all SQLAlchemy versions by using the UPPERCASE type objects
instead: :class:`_types.NVARCHAR`, :class:`_types.VARCHAR`,
:class:`_types.VARBINARY`, :class:`_types.TEXT`, :class:`_mssql.NTEXT`,
:class:`_mssql.IMAGE`
will always remain fixed and always output exactly that
type.
.. versionadded:: 1.0.0
.. _multipart_schema_names:
Multipart Schema Names
----------------------
SQL Server schemas sometimes require multiple parts to their "schema"
qualifier, that is, including the database name and owner name as separate
tokens, such as ``mydatabase.dbo.some_table``. These multipart names can be set
at once using the :paramref:`_schema.Table.schema` argument of
:class:`_schema.Table`::
Table(
"some_table", metadata,
Column("q", String(50)),
schema="mydatabase.dbo"
)
When performing operations such as table or component reflection, a schema
argument that contains a dot will be split into separate
"database" and "owner" components in order to correctly query the SQL
Server information schema tables, as these two values are stored separately.
Additionally, when rendering the schema name for DDL or SQL, the two
components will be quoted separately for case sensitive names and other
special characters. Given an argument as below::
Table(
"some_table", metadata,
Column("q", String(50)),
schema="MyDataBase.dbo"
)
The above schema would be rendered as ``[MyDataBase].dbo``, and also in
reflection, would be reflected using "dbo" as the owner and "MyDataBase"
as the database name.
To control how the schema name is broken into database / owner,
specify brackets (which in SQL Server are quoting characters) in the name.
Below, the "owner" will be considered as ``MyDataBase.dbo`` and the
"database" will be None::
Table(
"some_table", metadata,
Column("q", String(50)),
schema="[MyDataBase.dbo]"
)
To individually specify both database and owner name with special characters
or embedded dots, use two sets of brackets::
Table(
"some_table", metadata,
Column("q", String(50)),
schema="[MyDataBase.Period].[MyOwner.Dot]"
)
.. versionchanged:: 1.2 the SQL Server dialect now treats brackets as
identifier delimeters splitting the schema into separate database
and owner tokens, to allow dots within either name itself.
.. _legacy_schema_rendering:
Legacy Schema Mode
------------------
Very old versions of the MSSQL dialect introduced the behavior such that a
schema-qualified table would be auto-aliased when used in a
SELECT statement; given a table::
account_table = Table(
'account', metadata,
Column('id', Integer, primary_key=True),
Column('info', String(100)),
schema="customer_schema"
)
this legacy mode of rendering would assume that "customer_schema.account"
would not be accepted by all parts of the SQL statement, as illustrated
below::
>>> eng = create_engine("mssql+pymssql://mydsn", legacy_schema_aliasing=True)
>>> print(account_table.select().compile(eng))
SELECT account_1.id, account_1.info
FROM customer_schema.account AS account_1
This mode of behavior is now off by default, as it appears to have served
no purpose; however in the case that legacy applications rely upon it,
it is available using the ``legacy_schema_aliasing`` argument to
:func:`_sa.create_engine` as illustrated above.
.. versionchanged:: 1.1 the ``legacy_schema_aliasing`` flag introduced
in version 1.0.5 to allow disabling of legacy mode for schemas now
defaults to False.
.. _mssql_indexes:
Clustered Index Support
-----------------------
The MSSQL dialect supports clustered indexes (and primary keys) via the
``mssql_clustered`` option. This option is available to :class:`.Index`,
:class:`.UniqueConstraint`. and :class:`.PrimaryKeyConstraint`.
To generate a clustered index::
Index("my_index", table.c.x, mssql_clustered=True)
which renders the index as ``CREATE CLUSTERED INDEX my_index ON table (x)``.
To generate a clustered primary key use::
Table('my_table', metadata,
Column('x', ...),
Column('y', ...),
PrimaryKeyConstraint("x", "y", mssql_clustered=True))
which will render the table, for example, as::
CREATE TABLE my_table (x INTEGER NOT NULL, y INTEGER NOT NULL,
PRIMARY KEY CLUSTERED (x, y))
Similarly, we can generate a clustered unique constraint using::
Table('my_table', metadata,
Column('x', ...),
Column('y', ...),
PrimaryKeyConstraint("x"),
UniqueConstraint("y", mssql_clustered=True),
)
To explicitly request a non-clustered primary key (for example, when
a separate clustered index is desired), use::
Table('my_table', metadata,
Column('x', ...),
Column('y', ...),
PrimaryKeyConstraint("x", "y", mssql_clustered=False))
which will render the table, for example, as::
CREATE TABLE my_table (x INTEGER NOT NULL, y INTEGER NOT NULL,
PRIMARY KEY NONCLUSTERED (x, y))
.. versionchanged:: 1.1 the ``mssql_clustered`` option now defaults
to None, rather than False. ``mssql_clustered=False`` now explicitly
renders the NONCLUSTERED clause, whereas None omits the CLUSTERED
clause entirely, allowing SQL Server defaults to take effect.
MSSQL-Specific Index Options
-----------------------------
In addition to clustering, the MSSQL dialect supports other special options
for :class:`.Index`.
INCLUDE
^^^^^^^
The ``mssql_include`` option renders INCLUDE(colname) for the given string
names::
Index("my_index", table.c.x, mssql_include=['y'])
would render the index as ``CREATE INDEX my_index ON table (x) INCLUDE (y)``
.. _mssql_index_where:
Filtered Indexes
^^^^^^^^^^^^^^^^
The ``mssql_where`` option renders WHERE(condition) for the given string
names::
Index("my_index", table.c.x, mssql_where=table.c.x > 10)
would render the index as ``CREATE INDEX my_index ON table (x) WHERE x > 10``.
.. versionadded:: 1.3.4
Index ordering
^^^^^^^^^^^^^^
Index ordering is available via functional expressions, such as::
Index("my_index", table.c.x.desc())
would render the index as ``CREATE INDEX my_index ON table (x DESC)``
.. seealso::
:ref:`schema_indexes_functional`
Compatibility Levels
--------------------
MSSQL supports the notion of setting compatibility levels at the
database level. This allows, for instance, to run a database that
is compatible with SQL2000 while running on a SQL2005 database
server. ``server_version_info`` will always return the database
server version information (in this case SQL2005) and not the
compatibility level information. Because of this, if running under
a backwards compatibility mode SQLAlchemy may attempt to use T-SQL
statements that are unable to be parsed by the database server.
Triggers
--------
SQLAlchemy by default uses OUTPUT INSERTED to get at newly
generated primary key values via IDENTITY columns or other
server side defaults. MS-SQL does not
allow the usage of OUTPUT INSERTED on tables that have triggers.
To disable the usage of OUTPUT INSERTED on a per-table basis,
specify ``implicit_returning=False`` for each :class:`_schema.Table`
which has triggers::
Table('mytable', metadata,
Column('id', Integer, primary_key=True),
# ...,
implicit_returning=False
)
Declarative form::
class MyClass(Base):
# ...
__table_args__ = {'implicit_returning':False}
This option can also be specified engine-wide using the
``implicit_returning=False`` argument on :func:`_sa.create_engine`.
.. _mssql_rowcount_versioning:
Rowcount Support / ORM Versioning
---------------------------------
The SQL Server drivers may have limited ability to return the number
of rows updated from an UPDATE or DELETE statement.
As of this writing, the PyODBC driver is not able to return a rowcount when
OUTPUT INSERTED is used. This impacts the SQLAlchemy ORM's versioning feature
in many cases where server-side value generators are in use in that while the
versioning operations can succeed, the ORM cannot always check that an UPDATE
or DELETE statement matched the number of rows expected, which is how it
verifies that the version identifier matched. When this condition occurs, a
warning will be emitted but the operation will proceed.
The use of OUTPUT INSERTED can be disabled by setting the
:paramref:`_schema.Table.implicit_returning` flag to ``False`` on a particular
:class:`_schema.Table`, which in declarative looks like::
class MyTable(Base):
__tablename__ = 'mytable'
id = Column(Integer, primary_key=True)
stuff = Column(String(10))
timestamp = Column(TIMESTAMP(), default=text('DEFAULT'))
__mapper_args__ = {
'version_id_col': timestamp,
'version_id_generator': False,
}
__table_args__ = {
'implicit_returning': False
}
Enabling Snapshot Isolation
---------------------------
SQL Server has a default transaction
isolation mode that locks entire tables, and causes even mildly concurrent
applications to have long held locks and frequent deadlocks.
Enabling snapshot isolation for the database as a whole is recommended
for modern levels of concurrency support. This is accomplished via the
following ALTER DATABASE commands executed at the SQL prompt::
ALTER DATABASE MyDatabase SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE MyDatabase SET READ_COMMITTED_SNAPSHOT ON
Background on SQL Server snapshot isolation is available at
http://msdn.microsoft.com/en-us/library/ms175095.aspx.
N )information_schema )engine)exc)schema)sql)types)util)default)
reflection)compiler)
expression)func) quoted_name)BIGINT)BINARY)CHAR)DATE)DATETIME)DECIMAL)FLOAT)INTEGER)NCHAR)NUMERIC)NVARCHAR)SMALLINT)TEXT)VARCHARupdate_wrapper)public_factory)
) ) )
) ) )addallalterandanyasasc
authorizationbackupbeginbetweenbreakbrowsebulkbycascadecasecheck
checkpointclose clusteredcoalescecollatecolumncommitcompute
constraintcontains
containstablecontinueconvertcreatecrosscurrent current_date current_timecurrent_timestamp current_usercursordatabasedbcc
deallocatedeclarer deletedenydescdiskdistinct distributeddoubledropdumpelseenderrlvlescapeexceptexecexecuteexistsexitexternalfetchfile
fillfactorforforeignfreetext
freetexttablefromfullfunctiongotograntgrouphavingholdlockidentityidentity_insert identitycolifinindexinnerinsert intersectintoisjoinkeykillleftlikelinenoloadmergenationalnocheck nonclusterednotnullnullifofoffoffsetsonopenopendatasource openquery
openrowsetopenxmloptionororderouteroverpercentpivotplan precisionprimaryprintproc procedurepublic raiserrorreadreadtext reconfigure
references replicationrestorerestrictreturnrevertrevokerightrollbackrowcount
rowguidcolrulesaver
securityauditselect session_usersetsetusershutdownsome
statistics system_usertable tablesampletextsizethentotoptran transactiontriggertruncatetsequalunionuniqueunpivotupdate
updatetextuseuservaluesvaryingviewwaitforwhenwherewhilewith writetextc " e Zd Zd Z fdZ xZS )REALc t | dd t t | j di | d S )Nr )
setdefaultsuperr __init__)selfkw __class__s r/builddir/build/BUILD/cloudlinux-venv-1.0.12/venv/lib64/python3.11/site-packages/sqlalchemy/dialects/mssql/base.pyr z
REAL.__init__ sB
k2&&&"dD"((R((((( __name__
__module__ __qualname____visit_name__r
__classcell__r s @r r r s= N) ) ) ) ) ) ) ) )r r c e Zd Zd ZdS )TINYINTNr r r r r r r r r s NNNr r c : e Zd Zd Z ej d Zd ZdS )_MSDatec d }|S )Nc t | t j k r%t j | j | j | j S | S Ntypedatetimedateyearmonthdayvalues r processz'_MSDate.bind_processor..process 5 E{{hm++ (U[%)LLL r r r dialectr s r bind_processorz_MSDate.bind_processor r z(\d+)-(\d+)-(\d+)c fd}|S )Nc J t | t j r| S t | t j rYj | }|st d| d t j d | D S | S )Ncould not parse z as a date valuec 0 g | ]}t |pd S r int.0xs r
z=_MSDate.result_processor..process.. " &G&G&Gqs16{{&G&G&Gr )
isinstancer r r string_types_regmatch
ValueErrorgroupsr mr s r r z)_MSDate.result_processor..process %!233
zz||#E4#455
IOOE** $*@EG }&G&GAHHJJ&G&G&GHH r r r r coltyper s ` r result_processorz_MSDate.result_processor # r N)r r r r recompiler r r r r r r sF 2:* + +D r r c p e Zd Zd fd Z ej ddd Zd Z ej d Z
d Z xZ S ) TIMENc d || _ t t | d S r )r r r" r )r r kwargsr s r r z
TIME.__init__ s, "
dD""$$$$$r il r c fd}|S )Nc t | t j r8t j j | } n*t | t j r t | } | S r )r r combine_TIME__zero_datetimestr)r r s r r z$TIME.bind_processor..process so %!233
# )11$ejjll E8=11
# E
Lr r r s ` r r zTIME.bind_processor s# r z!(\d+):(\d+):(\d+)(?:\.(\d{0,6}))?c fd}|S )Nc J t | t j r| S t | t j rYj | }|st d| d t j d | D S | S )Nr z as a time valuec 0 g | ]}t |pd S r
r r
s r r z:TIME.result_processor..process.. r r ) r r r) r r r r r r r s r r z&TIME.result_processor..process r r r r s ` r r zTIME.result_processor r r r )
r r r r r r r( r r r r r r r s @r r" r" s % % % % % % (-a++K 2:: ; ;D r r" c e Zd Zd ZdS )
_DateTimeBasec d }|S )Nc t | t j k r%t j | j | j | j S | S r r r s r r z-_DateTimeBase.bind_processor..process r r r r s r r z _DateTimeBase.bind_processor r r N)r r r r r r r r/ r/ s# r r/ c e Zd ZdS ) _MSDateTimeNr r r r r r r3 r3 Dr r3 c e Zd Zd ZdS )
SMALLDATETIMENr r r r r7 r7 s $NNNr r7 c $ e Zd Zd Zd fd Z xZS ) DATETIME2Nc V t t | j di | || _ d S )Nr )r r9 r r )r r r r s r r zDATETIME2.__init__
s1 'i '--"---"r r r r s @r r9 r9 sB N# # # # # # # # # #r r9 c e Zd Zd ZddZdS )DATETIMEOFFSETNc || _ d S r r )r r r$ s r r zDATETIMEOFFSET.__init__ s
"r r )r r r r r r r r r< r< s- %N# # # # # #r r< c e Zd Zd ZdS )_UnicodeLiteralc fd}|S )Nc ~ | dd } j j r| dd } d| z S )N'z''%z%%zN'%s')replaceidentifier_preparer_double_percents)r r s r r z2_UnicodeLiteral.literal_processor..process sA MM#t,,E*;
1
c400U? "r r r s ` r literal_processorz!_UnicodeLiteral.literal_processor s# # # # # # r N)r r r rH r r r r@ r@ s#
r r@ c e Zd ZdS )
_MSUnicodeNr4 r r r rJ rJ % r5 r rJ c e Zd ZdS )_MSUnicodeTextNr4 r r r rL rL ) r5 r rL c 2 e Zd ZdZd ZdZddZ fdZ xZS ) TIMESTAMPaB Implement the SQL Server TIMESTAMP type.
Note this is **completely different** than the SQL Standard
TIMESTAMP type, which is not supported by SQL Server. It
is a read-only datatype that does not support INSERT of values.
.. versionadded:: 1.2
.. seealso::
:class:`_mssql.ROWVERSION`
NFc || _ dS )zConstruct a TIMESTAMP or ROWVERSION type.
:param convert_int: if True, binary integer values will
be converted to integers on read.
.. versionadded:: 1.2
N) convert_int)r rP s r r zTIMESTAMP.__init__A s 'r c x t t | || | j rfd}|S S )Nc h | } | #t t j | d d } | S )Nhex )r codecsencode)r super_s r r z+TIMESTAMP.result_processor..processP s6 u
$
eU ; ;R @ @E r )r rN r rP )r r r r rW r s @r r zTIMESTAMP.result_processorL sS y$''88'JJ
NMr F) r r r __doc__r lengthr r r r s @r rN rN - sd !N F ' ' ' '
r rN c e Zd ZdZd ZdS )
ROWVERSIONa( Implement the SQL Server ROWVERSION type.
The ROWVERSION datatype is a SQL Server synonym for the TIMESTAMP
datatype, however current SQL Server documentation suggests using
ROWVERSION for new datatypes going forward.
The ROWVERSION datatype does **not** reflect (e.g. introspect) from the
database as itself; the returned datatype will be
:class:`_mssql.TIMESTAMP`.
This is a read-only datatype that does not support INSERT of values.
.. versionadded:: 1.2
.. seealso::
:class:`_mssql.TIMESTAMP`
Nr r r rY r r r r r\ r\ \ s ( "NNNr r\ c e Zd ZdZd ZdS )NTEXTzMMSSQL NTEXT type, for variable-length unicode text up to 2^30
characters.Nr] r r r r_ r_ t s NNNr r_ c e Zd ZdZd ZdS ) VARBINARYaG The MSSQL VARBINARY type.
This type is present to support "deprecate_large_types" mode where
either ``VARBINARY(max)`` or IMAGE is rendered. Otherwise, this type
object is redundant vs. :class:`_types.VARBINARY`.
.. versionadded:: 1.0.0
.. seealso::
:ref:`mssql_large_type_deprecation`
Nr] r r r ra ra | s !NNNr ra c e Zd Zd ZdS )IMAGENr r r r rc rc NNNr rc c e Zd ZdZd ZdS )XMLa" MSSQL XML type.
This is a placeholder type for reflection purposes that does not include
any Python-side datatype support. It also does not currently support
additional arguments, such as "CONTENT", "DOCUMENT",
"xml_schema_collection".
.. versionadded:: 1.1.11
Nr] r r r rf rf s NNNr rf c e Zd Zd ZdS )BITNr r r r rh rh s NNNr rh c e Zd Zd ZdS )MONEYNr r r r rj rj rd r rj c e Zd Zd ZdS )
SMALLMONEYNr r r r rl rl s !NNNr rl c e Zd Zd ZdS )UNIQUEIDENTIFIERNr r r r rn rn s 'NNNr rn c e Zd Zd ZdS ) SQL_VARIANTNr r r r rp rp s "NNNr rp c & e Zd ZdZdZ fdZ xZS )TryCastz+Represent a SQL Server TRY_CAST expression.try_castc H t t | j |i | dS )a Create a TRY_CAST expression.
:class:`.TryCast` is a subclass of SQLAlchemy's :class:`.Cast`
construct, and works in the same way, except that the SQL expression
rendered is "TRY_CAST" rather than "CAST"::
from sqlalchemy import select
from sqlalchemy import Numeric
from sqlalchemy.dialects.mssql import try_cast
stmt = select([
try_cast(product_table.c.unit_price, Numeric(10, 4))
])
The above would render::
SELECT TRY_CAST (product_table.unit_price AS NUMERIC(10, 4))
FROM product_table
.. versionadded:: 1.3.7
N)r rr r )r argr r s r r zTryCast.__init__ s- . > %s1b11111r )r r r rY r r r r s @r rr rr sC 55 N2 2 2 2 2 2 2 2 2r rr z.dialects.mssql.try_castr bigintsmallinttinyintvarcharnvarcharcharnchartextntextdecimalnumericfloatr datetime2datetimeoffsetr )
r)
smalldatetimebinary varbinarybitrealimagexml timestampmoney
smallmoneyuniqueidentifier sql_variantc e Zd Zd dZd Zd Zd Zd Zd Zd Z d Z
d
Z d Z d Z
d
Zd Zd Zd Zd Zd Zd Zd Zd Zd Zd Zd Zd Zd Zd Z d Z d Z d Z d Z dS )!MSTypeCompilerNc t |dd r d|j z }nd}|s|j }|r|d|z z }d d ||fD S )zYExtend a string-type declaration with standard SQL
COLLATE annotations.
collationNz
COLLATE %s(%s) c g | ]}||S r r r cs r r z*MSTypeCompiler._extend..$ s GGGq r )getattrr rZ r )r spectype_rZ r s r _extendzMSTypeCompiler._extend sv 5+t , , $u6II I "\F *&6/)DxxGGT9$5GGGHHHr c : t |dd }|dS dd|iz S )Nr r zFLOAT(%(precision)s)r r r r r s r visit_FLOATzMSTypeCompiler.visit_FLOAT& s. E;55 7)[),DD Dr c dS )Nr r r r r s r
visit_TINYINTz MSTypeCompiler.visit_TINYINT- s yr c ( |j
d|j z S dS )NzDATETIMEOFFSET(%s)r< r> r s r visit_DATETIMEOFFSETz#MSTypeCompiler.visit_DATETIMEOFFSET0 s ? &'%/9 9##r c 6 t |dd }|d|z S dS )Nr zTIME(%s)r" r r s r
visit_TIMEzMSTypeCompiler.visit_TIME6 s) E;55 ) )6r c dS )NrN r r s r visit_TIMESTAMPz MSTypeCompiler.visit_TIMESTAMP= {r c dS )Nr\ r r s r visit_ROWVERSIONz MSTypeCompiler.visit_ROWVERSION@ |r c 6 t |dd }|d|z S dS )Nr z
DATETIME2(%s)r9 r r s r visit_DATETIME2z MSTypeCompiler.visit_DATETIME2C s) E;55 "Y. . ;r c dS )Nr7 r r s r visit_SMALLDATETIMEz"MSTypeCompiler.visit_SMALLDATETIMEJ s r c | j |fi |S r )visit_NVARCHARr s r
visit_unicodez MSTypeCompiler.visit_unicodeM s "t"5//B///r c R | j j r | j |fi |S | j |fi |S r )r deprecate_large_types
visit_VARCHAR
visit_TEXTr s r
visit_textzMSTypeCompiler.visit_textP sD < - 0%4%e22r22 2"4?5//B// /r c R | j j r | j |fi |S | j |fi |S r )r r r visit_NTEXTr s r visit_unicode_textz!MSTypeCompiler.visit_unicode_textV sE < - 1&4&u3333 3#4#E00R00 0r c . | d| S )Nr_ r r s r r zMSTypeCompiler.visit_NTEXT\ ||GU+++r c . | d| S )Nr r r s r r zMSTypeCompiler.visit_TEXT_ ||FE***r c @ | d||j pd S )Nr maxrZ r rZ r s r r z MSTypeCompiler.visit_VARCHARb s! ||IuU\5JU|KKKr c . | d| S )Nr r r s r
visit_CHARzMSTypeCompiler.visit_CHARe r r c . | d| S )Nr r r s r visit_NCHARzMSTypeCompiler.visit_NCHARh r r c @ | d||j pd S )Nr r r r r s r r z MSTypeCompiler.visit_NVARCHARk s! ||Jel6Ke|LLLr c d | j j t k r | j |fi |S | j |fi |S r )r server_version_infoMS_2008_VERSIONvisit_DATETIME
visit_DATEr s r
visit_datezMSTypeCompiler.visit_daten G < +o = =&4&u3333 3"4?5//B// /r c d | j j t k r | j |fi |S | j |fi |S r )r r r r r r s r
visit_timezMSTypeCompiler.visit_timet r r c R | j j r | j |fi |S | j |fi |S r )r r visit_VARBINARY visit_IMAGEr s r visit_large_binaryz!MSTypeCompiler.visit_large_binaryz sE < - 1'4'4444 4#4#E00R00 0r c dS )Nrc r r s r r zMSTypeCompiler.visit_IMAGE wr c dS )Nrf r r s r visit_XMLzMSTypeCompiler.visit_XML ur c @ | d||j pd S )Nra r r r r s r r z MSTypeCompiler.visit_VARBINARY s! ||Ku|7Lu|MMMr c , | | S r ) visit_BITr s r
visit_booleanz MSTypeCompiler.visit_boolean s ~~e$$$r c dS )Nrh r r s r r zMSTypeCompiler.visit_BIT r r c dS )Nrj r r s r visit_MONEYzMSTypeCompiler.visit_MONEY r r c dS )Nrl r r s r visit_SMALLMONEYz MSTypeCompiler.visit_SMALLMONEY r r c dS )Nrn r r s r visit_UNIQUEIDENTIFIERz%MSTypeCompiler.visit_UNIQUEIDENTIFIER s !!r c dS )Nrp r r s r visit_SQL_VARIANTz MSTypeCompiler.visit_SQL_VARIANT s }r r )!r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r s I I I I&E E E $ $ $ 0 0 00 0 0 1 1 1 , , ,+ + +L L L+ + +, , ,M M M0 0 0 0 0 0 1 1 1 N N N% % % " " " r r c B e Zd ZdZdZdZdZd Zd Zd Z d Z
d Z d Z dS ) MSExecutionContextFNc ^ | j j s | j | d S |S )Nr )r supports_unicode_statements_encoder)r statements r _opt_encodez MSExecutionContext._opt_encode s0 |7 <((33A6 6 r c | j r_| j j j }|j }|du}|r|j | j d v p| j j j o| j j j o6|j | j j j d v p|| j j j d v p<| j j j o*|j | j j j v p|| j j j v | _ nd| _ | j j
o |o | j j o| j o| j | _
| j rT| j | j | d| j | z d| dS dS dS )z#Activate IDENTITY_INSERT if needed.Nr FzSET IDENTITY_INSERT %s ONr )isinsertcompiledr r _autoincrement_columnr compiled_parameters
parameters_has_multi_parameters_enable_identity_insertinline returning executemany_select_lastrowidroot_connection_cursor_executerO r rF format_table)r tbl
seq_columninsert_has_sequences r pre_execzMSExecutionContext.pre_exec s = 3 -)/C 2J",D"8 "
5 Nd&>q&AA0 M+6 !M 3 I *#'=#:#Ea#H!I !I#-#'=#:#Ea#H$I !%
7 M M *#'=#:#E!F !F#-#'=#:#E$F' ,,4 05, M(( )')
//) 44) ((
" +
$44K$$3 2??DDE W3 3 T
r c \ | j }| j r| j j r | | j dd| n | | j dd| | j d }t |d | _ | j s| j
s| j r%| j j
rt j | | _ | j r\| | j | d| j | j j j z d| dS dS )z#Disable IDENTITY_INSERT if enabled.z$SELECT scope_identity() AS lastrowidr z SELECT @@identity AS lastrowidr SET IDENTITY_INSERT %s OFFN)r r r use_scope_identityr rO fetchallr
_lastrowidr isupdateisdeleter r r FullyBufferedResultProxy
_result_proxyr r rF r r r )r connrows r post_execz MSExecutionContext.post_exec sf # ! *|.
$$K: $$K!A2t +&&((+C !#a&kkDO
M G !] G.2m Gm% G "(!@!F!FD ' 0.;;
/5
r c | j S r )r r s r
get_lastrowidz MSExecutionContext.get_lastrowid s
r c | j rk | j | d| j | j j j z d S # t $ r Y d S w xY wd S )Nr )
r rO rc r rF r r r r Exception)r es r handle_dbapi_exceptionz)MSExecutionContext.handle_dbapi_exception s '
##$$4 2?? M 3 9
s AA" "
A0/A0c F | j r| j S t j | S r )r r ResultProxyr s r get_result_proxyz#MSExecutionContext.get_result_proxy s' ,% %%d++ +r )
r r r r r r r r r r r r r r r r r r s # MJ 6 6 6p$ $ $L , , , , ,r r c z e Zd ZdZ ej ej j ddddd Z fdZ fdZ
d Z d
Z d Z
d Zd
Zd Zd Zd Zd Zd Zd Zd Zd Zd Ze
d, fd Ze
fd Ze
d- fd Zd Z d Z d Z d Z fd Z d! Z!d" Z" fd#Z#d$ Z$d% Z%d& Z&d' Z'd( Z(d) Z)d* Z*d+ Z+ xZ,S ).
MSSQLCompilerT dayofyearweekday millisecond microsecond)doydow milliseconds microsecondsc V i | _ t t | j |i | d S r ) tablealiasesr r r )r argsr$ r s r r zMSSQLCompiler.__init__+ s3 +mT""+T.decorate0 s` |2
*r$+++++++ }d!;!;R[II vs)b)))r r )r* r+ r s ` r _with_legacy_schema_aliasingz*MSSQLCompiler._with_legacy_schema_aliasing/ s) * * * * * * r c dS )NCURRENT_TIMESTAMPr r r* r s r visit_now_funcz MSSQLCompiler.visit_now_func9 s ""r c dS )Nz GETDATE()r r/ s r visit_current_date_funcz%MSSQLCompiler.visit_current_date_func< r r c $ d | j |fi |z S NzLEN%sfunction_argspecr/ s r visit_length_funcz MSSQLCompiler.visit_length_func? # ..r88R8888r c $ d | j |fi |z S r4 r5 r/ s r visit_char_length_funcz$MSSQLCompiler.visit_char_length_funcB r8 r c T | j |j fi |d | j |j fi |S )Nz + r r r r r operatorr s r visit_concat_op_binaryz$MSSQLCompiler.visit_concat_op_binaryE sG DL + + + + + + DL , , , , ,
r c dS )N1r r exprr s r
visit_truezMSSQLCompiler.visit_trueK sr c dS )N0r rB s r visit_falsezMSSQLCompiler.visit_falseN rE r c X d | j |j fi |d | j |j fi |dS )Nz
CONTAINS (, )r< r= s r visit_match_op_binaryz#MSSQLCompiler.visit_match_op_binaryQ sL DL + + + + + + DL , , , , , ,
r c d}|j r|dz
}|j r&|j |j r|j dk r
|d|j z z
}|r|S t
j j | |fi |S )z- MS-SQL puts TOP, it's version of LIMIT here z DISTINCT Nr zTOP %d ) _distinct_simple_int_limit_offset_clause_simple_int_offset_offset_limitr SQLCompilerget_select_precolumns)r r r ss r rV z#MSSQLCompiler.get_select_precolumnsW s
A # + ! ))
*.4n.A.A
V]* *A H'=f "
r c |S r r r r r} s r get_from_hint_textz MSSQLCompiler.get_from_hint_textn r c |S r r rY s r get_crud_hint_textz MSSQLCompiler.get_crud_hint_textq r[ r c dS NrN r )r r r s r limit_clausezMSSQLCompiler.limit_clauset s rr c X d | j |j fi |d | j |j fi |dS )Nz
TRY_CAST (z AS rK )r clause
typeclause)r elementr s r visit_try_castz MSSQLCompiler.visit_try_castx sM DL . .2 . . . . DL+ 2 2r 2 2 2 2
r c |j s|j |j |j r|j rt |dd sy|j j st j d d |j j D }|j }|j }||d< |
}d|_ | t j | d d }t j d }t j d |j D }|8| ||k | | |||z k n| ||k | j |fi |S t1 j j | |fi |S )
zLook for ``LIMIT`` and OFFSET in a select statement, and if
so tries to wrap it in a subquery with ``row_number()`` criterion.
N _mssql_visitzLMSSQL requires an order_by when using an OFFSET or a non-simple LIMIT clausec 6 g | ]}t j | S r )sql_utilunwrap_label_reference)r elems r r z.MSSQLCompiler.visit_select.. s3 ! ! ! /55! ! !r select_wraps_forTorder_bymssql_rnc ( g | ]}|j d k
|S )ro )r r s r r z.MSSQLCompiler.visit_select.. s$ << 2 &.$77 2 *2
&# ! ! " 3 ;! ! !
"/L " 1M)/F% &%%''F"&F
H''))T#4T55U:&&
$
z*--H *<yOOBOOO6u]D))6
&7
;=
r c t |dd 2|| j vr | | j |< | j | S d S )Nr )r r% rx )r r s r r z#MSSQLCompiler._schema_aliased_table sJ 5(D ) ) 5D ---+0;;==!%($U+ +4r c | j |j |j }d|d | j |j fi |dS )Nz DATEPART(rJ rK ) extract_mapgetfieldr rC )r extractr r s r
visit_extractzMSSQLCompiler.visit_extract sK $$W]GMBB%*UULDL ,L,L,L,L,L,LMMr c < d| j | z S )NzSAVE TRANSACTION %spreparerformat_savepointr savepoint_stmts r visit_savepointz MSSQLCompiler.visit_savepoint s& $t}'E'E (
(
r c < d| j | z S )NzROLLBACK TRANSACTION %sr r s r visit_rollback_to_savepointz)MSSQLCompiler.visit_rollback_to_savepoint s& (4=+I+I ,
,
r c N t |j t j re|j t j k rPt |j t j s1 | j t j |j |j |j fi |S t t | j |fi |S )z]Move bind parameters to the right-hand side of an operator, where
possible.
) r r r
BindParameterr> eqr r BinaryExpressionr r visit_binary)r r r$ r s r r zMSSQLCompiler.visit_binary s
v{J$< = =
8;.. v|Z-EFF / 4<+L&+v
7u]D))6vHHHHHr c & j s j r|j d }n|j d }t j | fdt
j | D }dd | z S )Ninserteddeletedc h g | ].} d | ddi /S )NTF)_label_select_columntraverse)r r adapterr s r r z2MSSQLCompiler.returning_clause.. sT
% %g&&q))4
r zOUTPUT rJ ) r r r rx ri
ClauseAdapterr _select_iterablesr )r stmtreturning_colstargetcolumnsr s ` @r returning_clausez MSSQLCompiler.returning_clause
s = 1DM 1Z%%j11FFZ%%i00F(00
1.AA
499W----r c dS )NWITHr )r recursives r get_cte_preamblez MSSQLCompiler.get_cte_preamble s
vr c t |t j r| d S t t
| ||| S r )r r Functionrw r r label_select_column)r r r@ asfromr s r r z!MSSQLCompiler.label_select_column& sS fj 1 2 2 <<%% % --AA
r c dS r_ r )r r s r for_update_clausez MSSQLCompiler.for_update_clause. s rr c t | r |j sdS | j |j fi |}|rd|z S dS )NrN z
ORDER BY )r rT r rr )r r r rn s r order_by_clausez MSSQLCompiler.order_by_clause3 sZ fm 2 4< 7>>2>> (* *2r c \ dd fd|g|z D z S )a Render the UPDATE..FROM clause specific to MSSQL.
In MSSQL, if the UPDATE statement involves an alias of the table to
be updated, then the table itself must be added to the FROM list as
well. Otherwise, it is optional. Here, we add it regardless.
FROM rJ c 3 : K | ]} |j fd dV dS T)r fromhintsN_compiler_dispatchr r
from_hintsr r s r z3MSSQLCompiler.update_from_clause..L S #
#
!A Odj O OB O O#
#
#
#
#
#
r r )r update_stmt
from_table extra_fromsr r s ` ``r update_from_clausez MSSQLCompiler.update_from_clauseB s[ #
#
#
#
#
#
\K/#
#
#
r c @ d}|rd}| | dd| S )z=If we have extra froms make sure we render any alias as hint.FT)r r ashintr )r delete_stmtr r r s r delete_table_clausez!MSSQLCompiler.delete_table_clauseQ s: F,, d6 -
r c \ dd fd|g|z D z S )zjRender the DELETE .. FROM clause specific to MSSQL.
Yes, it has the FROM keyword twice.
r rJ c 3 : K | ]} |j fd dV dS r r r s r r z9MSSQLCompiler.delete_extra_from_clause..b r r r )r r r r r r s ` ``r delete_extra_from_clausez&MSSQLCompiler.delete_extra_from_clauseZ s[ #
#
#
#
#
#
\K/#
#
#
r c dS )NzSELECT 1 WHERE 1!=1r )r r s r visit_empty_set_exprz"MSSQLCompiler.visit_empty_set_exprg s $$r c t d| |j d| |j dS )NzNOT EXISTS (SELECT INTERSECT SELECT rK r< r= s r visit_is_distinct_from_binaryz+MSSQLCompiler.visit_is_distinct_from_binaryj < LL % % % % LL & & & &
r c t d| |j d| |j dS )NzEXISTS (SELECT r rK r< r= s r visit_isnot_distinct_from_binaryz.MSSQLCompiler.visit_isnot_distinct_from_binaryp r r )FFr )-r r r returning_precedes_valuesr update_copyr rU r r r, r0 r2 r7 r: r? rD rH rL rV rZ r] r` re rz r r r r r r r r r r r r r r r r r r r r r s @r r r s $ "$" ( ) )
K= = = = = # # # 9 9 99 9 9
.
8M 8M 8Mt " K K K K K "! K "C C C C "!C
"
"!
4 N N N
I I I I I$. . .$
% % %
r r c 2 e Zd ZdZdZd Zd Z fdZ xZS )MSSQLStrictCompilerzA subclass of MSSQLCompiler which disables the usage of bind
parameters where not allowed natively by MS-SQL.
A dialect may use this compiler on a platform where native
binds are used.
Tc ^ d|d< | j |j fi |d | j |j fi |S )NT
literal_bindsz IN r< r= s r visit_in_op_binaryz&MSSQLStrictCompiler.visit_in_op_binary Q "? DL + + + + + + DL , , , , ,
r c ^ d|d< | j |j fi |d | j |j fi |S )NTr z NOT IN r< r= s r visit_notin_op_binaryz)MSSQLStrictCompiler.visit_notin_op_binary r r c t t | t j rdt | z dz S t t | || S )a5
For date and datetime values, convert to a string
format acceptable to MSSQL. That seems to be the
so-called ODBC canonical date format which looks
like this:
yyyy-mm-dd hh:mi:ss.mmm(24h)
For other data types, call the base class implementation.
rC )
issubclassr r r r* r r render_literal_value)r r r r s r r z(MSSQLStrictCompiler.render_literal_value s] d5kk8= 1 1 U#c) ),d33HHu
r ) r r r rY ansi_bind_rulesr r r r r s @r r r w sg O
r r c 4 e Zd Zd Zd dZd Zd Zd Zd ZdS )
MSDDLCompilerc | j | }|j !|d| |j z z
}n,|d| j j |j | z z
}|j H|j r/|j s(t |j
t j s |j
du r|dz
}n |j |dz
}|j t j d t |j
t j rt|j
j |j
j ||j j urt) j d |j
j dk rd}n|j
j pd }|d
|d |j
j pd d z
}ni||j j u s |j
du r3|j d
d }|j d
d }|d
|d |d z
}n | | }||d|z z
}|S )Nr )type_expressionTz NOT NULLz NULLz;mssql requires Table-bound columns in order to generate DDLa
Use of Sequence with SQL Server in order to affect the parameters of the IDENTITY value is deprecated, as Sequence will correspond to an actual SQL Server CREATE SEQUENCE in a future release. Please use the mssql_identity_start and mssql_identity_increment parameters.r r z
IDENTITY(,rK mssqlidentity_startidentity_incrementz DEFAULT )r
format_columncomputedr r
type_compilerr nullable primary_keyr r sa_schemaSequence
autoincrementr r rt start incrementr r warn_deprecateddialect_optionsget_column_default_string)r r@ r$ colspecr r r s r get_column_specificationz&MSDDLCompiler.get_column_specification s; ---f55 ? & sT\\&/ : :: :GG sT\ 7 ? ? V @
G ? &O
#%
# fni.@AA
# '4//;& (7" < "+
fni&8 9 9 # 1 $0>+7 !CCC$? ~#q(( ,1 G(-A--
GG
fl8 8 8#t++*734DEE .w78LMI GUUUIII> >GG44V<. sX !))T * r rK includec l g | ]0}t |t j rj j | n|1S r )r r r r r )r colr{ s r r z4MSDDLCompiler.visit_create_index..
sN c4#455
c"" r z
INCLUDE (%s)c D g | ] } |j S r )quoter )r r r s r r z4MSDDLCompiler.visit_create_index.. s' <<.wrap sO &w77
r r r r* rN s ` r _db_plus_owner_listingrP s3
$ # ##r c 0 d fd }t | S )Nc T t | | \ }}t ||| |||||f i |S r rJ )r rM tablenamer r rB rC r* s r rN z _db_plus_owner..wrap sR &w77
r r r rO s ` r _db_plus_ownerrT s3
$ # ##r c | rP| d }|| k r5| d|j j | z ||i || r<|| k r7| d|j j | z S S S # | r<|| k r7| d|j j | z w w w xY w)Nzselect db_name()zuse %s)scalarrc r rF r )rB rM r* ru r
current_dbs r rL rL s"
&&'9::
:-AGGOOO
r3~"~~ jF** $8>>zJJK
*6 jF** $8>>zJJK
*s
B AC c F |s d | j fS d|v rt | S d |fS )Nr? )default_schema_namer@ )r r s r rK rK s9 W000 '''V|r c t | t r | j rd | fS | t v r
t | S g }d}d}d}t j d| D ][}|s|dk rd}d}|dk rd}|s;|dk r5|r| d|z n| | d}d}V||z
}\|r| | t | d k r}d |d
d |d }}t j d |d d rt |d
}nH|
d d }n t | r d |d
}}nd\ }}||ft | < ||fS )NrN Fz
(\[|\]|\.)r2 Tr3 r? z[%s]r r z
.*\].*\[.*r )NN) r r r _memoized_schemar splitappendr" r r lstriprstrip)r pushsymbolbracket has_bracketstokenrB rC s r r@ r@ s &+&& 6< V|
!!! '' D
FGL-00 C<<G LL
c\\GG Uc\\
$ FVO,,,, F###F LL eOFF
F
4yy1}}ad,,d2h 8M6!B$< 0 0 4 u555FF]]3''..s33FF T # d1g"
%u}V 5=r c
D e Zd ZdZdZdZeZdZdZ dZ
e j e
e j ee j ee j ee j eiZej j dej fg Ze Z dZ dZ dZ dZ!dZ"dZ#e$Z%e&Z'e(Z)e*Z+e,j- dd ife,j. dd ife,j/ d d d d
fe,j0 d d d fgZ1 d! fd
Z2 fdZ3d Z4 e5g d Z6d Z7d Z8 fdZ9d Z:d Z;d Zd Z?e@jA d ZBe@jA eCd ZDe@jA eCd ZEe@jA e>d ZFe@jA e>d ZGe@jA e>d ZHe@jA e>d ZIe@jA e>d ZJ xZKS )" MSDialectr TF dbor) r r= N)r= r
r r )r r c t |pd | _ || _ || _ || _ || _ t
t | j di | || _ d S )Nr r )
r
query_timeout schema_namer r r) r rh r isolation_level) r rl r rm rn r r) optsr s r r zMSDialect.__init__, sk ! !3! 4 4&"4 %:"&<#'i '//$/// . r c | d t t | || d S )Nz$IF @@TRANCOUNT = 0 BEGIN TRANSACTION)rc r rh do_savepoint)r rM r r s r rq zMSDialect.do_savepointA s> ABBB
i ++J=====r c d S r r )r rM r s r do_release_savepointz MSDialect.do_release_savepointF s r ) SERIALIZABLEzREAD UNCOMMITTEDzREAD COMMITTEDzREPEATABLE READSNAPSHOTc
p | dd }|| j vr:t j d|d| j dd | j | }| d|z | |dk r| d S d S ) N_r zInvalid value 'z2' for isolation_level. Valid isolation levels for z are rJ z"SET TRANSACTION ISOLATION LEVEL %sru )
rE _isolation_lookupr
ArgumentErrorr r rO rc r< rA )r rM levelrO s r set_isolation_levelz MSDialect.set_isolation_levelT s
c3'' . . .## 55$)))TYYt/E%F%F%FH
""$$;eCDDD J r c & | j t k rt d d }d}|D ]}| } | d|z | d }| | c S # | j j $ r }|}Y d }~| d }~ww xY w# | w xY wt j d|d| t d|d| )Nz4Can't fetch isolation level prior to SQL Server 2005)zsys.dm_exec_sessionsz sys.dm_pdw_nodes_exec_sessionsa
SELECT CASE transaction_isolation_level
WHEN 0 THEN NULL
WHEN 1 THEN 'READ UNCOMMITTED'
WHEN 2 THEN 'READ COMMITTED'
WHEN 3 THEN 'REPEATABLE READ'
WHEN 4 THEN 'SERIALIZABLE'
WHEN 5 THEN 'SNAPSHOT' END AS TRANSACTION_ISOLATION_LEVEL
FROM %s
where session_id = @@SPID
r z:Could not fetch transaction isolation level, tried views: z; final error was: zPCan't fetch isolation level on this particular SQL Server version. tried views: ) r MS_2005_VERSIONNotImplementedErrorrO rc fetchoneupperr< dbapiErrorr warn)r rM
last_errorviewsr rO valerrs r get_isolation_levelz MSDialect.get_isolation_levelb s] #o 5 5%F
J % % D &&((F
oo''* yy{{ :#
II:?%%M
&% 55**&
s/ 2B/C C(C*C CC C!c t t | | | | | d S r )r rh
initialize_setup_version_attributes _setup_supports_nvarchar_max)r rM r s r r zMSDialect.initialize sM
i ))*555 &&((( ))*55555r c $ j fd}|S d S )Nc > | j d S r )r{ rn )r
r s r connectz%MSDialect.on_connect..connect s" ((t/CDDDDDr )rn )r r s ` r
on_connectzMSDialect.on_connect s6 +
E
E
E
E
E N4r c v | j d t t dd vr9t j dd d | j D z | j t k rd| j vrd| _ | j t k rd| _
| j | j t k | _ d S d S ) Nr r( z[Unrecognized server version info '%s'. Some SQL Server features may not function properly.r? c 3 4 K | ]}t | V d S r )r* r
s r r z6MSDialect._setup_version_attributes.. s( DDa3q66DDDDDDr implicit_returningT)
r listranger r r r} __dict__r r supports_multivalues_insertr MS_2012_VERSIONr s r r z#MSDialect._setup_version_attributes s #A &d5B<<.@.@ @ @ I6((DD4+CDDDDDE
$ 7 7$DM99&*D # # 6 6/3D , % -(O;
& & & . -r c | t j d d| _ d S # t j $ r d| _ Y d S w xY w)Nz0SELECT CAST('test max support' AS NVARCHAR(max))TF)rV r r} _supports_nvarchar_maxr
DBAPIError)r rM s r r z&MSDialect._setup_supports_nvarchar_max sm / KLL
+/D ' ' ' ~ 0 0 0*/D ' ' ' ' 0s '2 A A c | j t k r| j S t j d }| | }|t
|d S | j S )NzSELECT schema_name()Tr\ )r r} rm r r} rV r )r rM queryrY s r _get_default_schema_namez"MSDialect._get_default_schema_name sb #o 5 5# #H 344E","3"3E":": ". ##6dCCCC''r c t j }|j j |k }|r#t j ||j j |k }t j |g| }| | } | d uS r )
ischemar r
table_namer and_ table_schemar rc first)
r rM rS rB rC r r r rW r s
r has_tablezMSDialect.has_table s{ / i*i7 (WY 3u < K
Jy+ . . q ! !wwyy$$r c t j t j j j gt j j j g }d | | D }|S )Nrm c g | ]
}|d S r
r r rs r r z.MSDialect.get_schema_names.. s <<<!<<. s ;;;qt;;;r
r tablesr r r r r r
table_typerc ) r rM rB rC r r r rW table_namess r get_table_nameszMSDialect.get_table_names s J
X
! H%.#|3
h)*
<;Z%7%7%:%:;;; r c t j }t j |j j gt j |j j |k |j j dk |j j g }d | | D }|S )NVIEWrm c g | ]
}|d S r
r r s r r z,MSDialect.get_view_names.. s :::qad:::r r ) r rM rB rC r r r rW
view_namess r get_view_nameszMSDialect.get_view_names s J
X
! H%.0Cv0M
h)*
;:J$6$6q$9$9:::
r c | j t k rg S | t j d t j d|t j t j d|t j t j }i }|D ]!} | d | d dk g d|| d < "| t j d
t j d|t j t j d|t j t j }|D ]9} | d |v r-|| d d | d :t | S ) Na select ind.index_id, ind.is_unique, ind.name from sys.indexes as ind join sys.tables as tab on ind.object_id=tab.object_id join sys.schemas as sch on sch.schema_id=tab.schema_id where tab.name = :tabname and sch.name=:schname and ind.is_primary_key=0 and ind.type != 0tabnameschname)r r is_uniquer )r r column_namesindex_idaR select ind_col.index_id, ind_col.object_id, col.name from sys.columns as col join sys.tables as tab on tab.object_id=col.object_id join sys.index_columns as ind_col on (ind_col.column_id=col.column_id and ind_col.object_id=tab.object_id) join sys.schemas as sch on sch.schema_id=tab.schema_id where tab.name=:tabname and sch.name=:schnamer )r r} rc r r}
bindparams bindparamr
CoerceUnicoder sqltypesUnicoder_ r r )
r rM rS rB rC r r rpindexesr s
r get_indexeszMSDialect.get_indexes s
#o 5 5I
H=
Z
iG4I4K4KLL
i0E0G0GHH W(*,,W
-
-
CF k*a/ "( (GC
O $ $
H(
Z
iG4I4K4KLL
i0E0G0GHH W(*,,W
-
-!
$ M MC:'))J( 8??F LLLGNN$$%%%r c @ | t j d t j d|t j t j d|t j }|r| }|S d S )Nzselect definition from sys.sql_modules as mod, sys.views as views, sys.schemas as sch where mod.object_id=views.object_id and views.schema_id=sch.schema_id and views.name=:viewname and sch.name=:schnameviewnamer )rc r r} r r r r rV ) r rM r rB rC r r r view_defs r get_view_definitionz MSDialect.get_view_definition6
s
H=
j
j(G4I4K4KLL
i0E0G0GHH
yy{{HO r c
| t j }t j }|rwt j |j j |k |j j |k } |d|}
|j j dz |j j z } |j j t j | k } n>|j j |k } |}
|j j t j |j j k } t j | |j j
|j j k } | || d }
| j
r
|j j }n,t j |j j t! d }t j |||j j g| |
|j j g }| | }g } | }|n||j j
}||j j }||j j dk }||j j }||j j }||j j }||j j }||j j }|| }||j j } | j |d } i } | t> t@ tB tD tF tH tJ tL tN j( f v r|dk rd }|| d< |r|| d < | (tS j* d
|d |d tN j+ } nFtY | tN j- r$|| d
< tY | tN j. s|| d< | d!i | } || ||dd} |
| || d| d< |/ | i } |D ]
}!|!| |!d < | t j0 d ||d }"d }# |" }|nF|d |d }%}$|%1 d r |$| v r |$}#d| |$ d< ddd| |$ d < n]|"2 |#| j3 th k r|d|}
| d |
d |
d }"|"5 }|R|d J| |# d 6 to |d to |d d |S )"Nr? T)onclauseisouteri )from_objrn YESr[ rZ r zDid not recognize type 'z
' of column 'rC r scaleF)r r r r r )r+ r, r r zFEXEC sp_columns @table_name = :table_name, @table_owner = :table_owner)r table_ownerr rv r r )mssql_identity_startmssql_identity_incrementr zselect ident_seed('z'), ident_incr('z')r r )8r r computed_columnsr r r r r object_idr column_namer r r
definitioncastr r is_persistedordinal_positionrc r data_type is_nullablecharacter_maximum_lengthnumeric_precision
numeric_scalecolumn_defaultcollation_name
ischema_namesr MSStringMSChar
MSNVarcharMSNCharMSTextMSNTextMSBinary MSVarBinaryr LargeBinaryr r NULLTYPEr NumericFloatr_ r} endswithr< r r} r r r )&r rM rS rB rC r r r
computed_colsr table_fullname full_namejoin_onr computed_definitionrW r colsr r r r charlen numericprec numericscaler r r r r r$ cdictcolmapr rO iccol_name type_names& r get_columnszMSDialect.get_columnsN
sT / 0
( $ 1 &%/ K ).yy 9N .4wy7KKI#o/4>)3L3LLGG!).);K &N#o/4> $4 4 G ( WY*mo.BB
||MGT|JJ & "//"< #&( *HTNN# #
J
)=?+G H i01
q ! !? **,,C{wy,-D +,E7901U:H')<=G gi 9:K wy 67L')23GGI 45I 01J } ;> 7*6w!'++F++ $"!& E %,*B )!-% %j!
KK ? B & &C"%F3v; ## H.
%U ; ;
//##C{$'FCFyX!!*--
(f2D2D 48x 1,-017 7x !23
>d 6/ I I(-yy 9N '''!>>>>>3 F
,,..C3q6#5r
,-4403CF 47AKK r c
g }t j }t j d } t j | j j |j j | j j gt j
|j j | j j k |j j | j j k | j j |k | j j |k
|j j | j j }
| |
} d } | D ]O}
d|
|j j j v r4| |
d | |
| j j j } P|| dS )NCPRIMARYr )constrained_columnsr )r constraintskey_constraintsrx r r r r constraint_typeconstraint_namer r r rn r rc r r_ )r rM rS rB rC r r pkeysTCr rW r r r s r get_pk_constraintzMSDialect.get_pk_constraint
s<
# ) )# . .
J
S_bd 2AC4G H H$(;;!QS%55)+ E)
(24')=
>
>
q ! ! D DCC 4 9 ::: SV$$$"*&)!#*=*B&CO',oFFFr c
t j }t j d }t j d } t j |j j | j j | j j | j j |j j
|j j |j j |j j
gt j |j j |k |j j |k |j j |j j k |j j
|j j
k | j j
|j j k | j j |j j k |j j | j j k |j j
| j j g }
g } d } t' j | } | |
D ]x}
|
\ }}}}}}}}| | }||d< |d s ||d< |||k r|r|dz |z }||d< |d |d
}}| | | | yt1 | S ) Nr Rrm c d g d d g dS )N)r r referred_schemareferred_tablereferred_columnsr r r r fkey_recz,MSDialect.get_foreign_keys..fkey_rec' s ')#'"&$&
r r r r? r r r )r ref_constraintsr rx r r r r r r r match_option update_rule delete_ruler constraint_schemaunique_constraint_nameunique_constraint_schemar r defaultdictrc r r_ r r )r rM rS rB rC r r RRr r
rW fkeysr r scolrschemartblrcolrfknmfkmatchfkuprule fkdelrulerec
local_cols remote_colss r get_foreign_keyszMSDialect.get_foreign_keys sK
$ # ) )# . . # ) )# . .
J $!
H)+ E)&!#*::#rt';;#rt'BB%)FF$(<<
d*AC,@A)
0 **##A&&//11 % %AMN JD'4ugx,C CK'(
5(,$%%')9)9 9"(3,"8-4C)* )*&' $J
d # # # t $ $ $ $ELLNN###r )NTrj NNF)Lr r r r supports_default_valuessupports_empty_insertr execution_ctx_clsr max_identifier_lengthrm r DateTimer3 Dater Timer" r rJ UnicodeTextrL colspecsr DefaultDialectengine_config_typesr r asboolr supports_native_boolean#non_native_boolean_check_constraintsupports_unicode_bindspostfetch_lastrowidr r r statement_compilerr ddl_compilerr r r0 r r PrimaryKeyConstraintUniqueConstraintIndexColumnconstruct_argumentsr rq rs r rx r{ r r r r r r rT r r
cacher rP r r r r r r r( r r s @r rh rh s D " !* K ;
w
t* n H "0DJJ
"DK 01 "M #*/' ! " & L"M#H
'+t)<= #k4%89 MMN aqIIJ " $/ / / / / /*> > > > >
. . .`6 6 6 6 6
&/ / / ( ( ( % % ^ %
3& 3& ^ 3&j ^ , U U ^ Un G G ^ G4 A$ A$ ^ A$ A$ A$ A$ A$r rh )rY rU r r> r rN r r r r r r r r
r r r r
r r r r ri r r r r r r r r r r r r r r r! util.langhelpersr" MS_2016_VERSIONMS_2014_VERSIONr r r} MS_2000_VERSIONr rF r Integerr r. r r" _MSTimeobjectr/ r- r3 r7 r9
TypeEnginer< r@ r rJ r0 rL _BinaryrN r\ r_ ra r rc Textrf rh rj rl rn rp elementsCastrr rs
MSDateTimeMSDateMSReal
MSTinyIntegerMSTimeMSSmallDateTime MSDateTime2MSDateTimeOffsetr r r r r r r r MSImageMSBitMSMoney MSSmallMoneyMSUniqueIdentifier MSVariantr GenericTypeCompilerr DefaultExecutionContextr rU r r DDLCompilerr IdentifierPreparerr0 rP rT rL rK LRUCacher] r@ r2 rh r r r r` s;
e
e
N
+ + + + + + # # # # # # ! ! ! ! ! ! # # # # # # " " " " " " . . . . . . u u uw wt) ) ) ) )8= ) ) ) h hm :' ' ' ' '8= ' ' 'T F -!2 % % % % %M8#4 % % %# # # # #
x 0 # # ## # # # #X( # # # f ("2 _h&: , , , , , , , ,^" " " " " " " "0 H ! ! ! ! !"H$8 ! ! !( H (- (
H " " " " "$ " " "( ( ( ( (x* ( ( (# # # # #(% # # # 2 2 2 2 2cl 2 2 2> >'#= > >
!
% 7 f w
w
D U D U w w U n! " D# $
"
( =
DG G G G G X1 G G G T, , , , ,8 , , ,DV
V
V
V
V
H( V
V
V
r
, , , , ,- , , ,^t t t t tH( t t tn( ( ( ( (86 ( ( (V$ $ $$$ $ $& " !4=?? 4 4 4nE $ E $ E $ E $ E $& E $ E $ E $ E $ E $r