o [hc@s dZddlZddlZddlZddlZddlmZddlmZddlm Z ddlm Z dd lm Z dd lm Zdd lmZdd lmZdd lmZddl mZddl mZddl mZddl mZdd l mZddl mZddl mZddl mZddl mZddl mZddl mZddl mZddl mZddl mZddl m Z ddl m!Z!ddl m"Z"ddl m#Z#ddl m$Z$dd lm%Z%dd!l&m'Z'd"Z(d#Z)d$Z*d%Z+d&Z,d'Z-e.gd(Z/Gd)d*d*ej0Z0Gd+d,d,ej1Z2Gd-d.d.ej3Z4Gd/d0d0ej5Z5e5Z6Gd1d2d2e7Z8Gd3d4d4e8ej9Z:Gd5d6d6e8ej9Z;Gd7d8d8e8ej9ZGd;d<dd>e?ej@ZAGd?d@d@e?ejBZCGdAdBdBejDZEGdCdDdDeEZFGdEdFdFejBZGGdGdHdHejHejIZHGdIdJdJejIZJGdKdLdLejKZLGdMdNdNej=ZMGdOdPdPej=ZNGdQdRdRej=ZOGdSdTdTej=ZPGdUdVdVej=ZQGdWdXdXe jRjSZTe'eTdYZUe:ZVe4ZWe0ZXe2ZYe5ZZe;Z[eZ]e#Z^eGZ_e$Z`e!ZaeZbeZceZdeHZeeJZfeMZgeNZheOZiePZjeQZkidZed[ed\e"d]e2d^e$d_e!d`edaedbe#dceGddedee dfedgedhe<die>djee5e;eeHeMe0eJeLeEeNeOePeQdk ZlGdldmdmejmZnGdndodoejoZpGdpdqdqejqZrGdrdsdserZsGdtduduejtZuGdvdwdwejvZwdxdyZxdzd{Zyd|d}Zzd~dZ{e|Z}ddZ~GdddejZdS)aY .. dialect:: mssql :name: Microsoft SQL Server .. _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) ) ) ) ) ))addallZalterandanyasasc authorizationbackupbeginZbetweenbreakZbrowseZbulkZbyZcascadecasecheck checkpointclose clusteredZcoalesceZcollatecolumncommitZcompute constraintcontainsZ containstablecontinueconvertcreatecrosscurrentZ current_date current_timeZcurrent_timestamp current_usercursorZdatabaseZdbccZ deallocateZdeclarer deleteZdenyZdescZdiskZdistinct distributeddoubledropdumpelseendZerrlvlescapeexceptexecexecuteexistsexitZexternalfetchfileZ fillfactorforZforeignZfreetextZ freetexttablefromfullfunctionZgotoZgrantgroupZhavingZholdlockidentityZidentity_insertZ identitycolifinindexinnerinsertZ intersectZintoisjoinkeykillleftlikelinenoloadmergeZnationalZnocheckZ nonclusterednotnullZnullifZofoffoffsetsonopenZopendatasourceZ openqueryZ openrowsetZopenxmloptionororderouteroverpercentZpivotZplan precisionprimaryprintprocZ procedurepublicZ raiserrorreadZreadtext reconfigureZ referencesZ replicationZrestoreZrestrictreturnrevertZrevokerightrollbackZrowcountZ rowguidcolrulesaverZ securityauditselectZ session_usersetZsetusershutdownZsome statisticsZ system_usertableZ tablesampleZtextsizeZthentotopZtranZ transactiontriggertruncateZtsequalunionuniqueZunpivotupdateZ updatetextZuseuservaluesZvaryingviewZwaitforwhenwherewhilewithZ writetextcs eZdZdZfddZZS)REALc s&|ddtt|jdi|dS)Nrr) setdefaultsuperr__init__)selfkw __class__r/home/ubuntu/experiments/live_experiments/Pythonexperiments/Otree/venv/lib/python3.10/site-packages/sqlalchemy/dialects/mssql/base.pyrs z REAL.__init____name__ __module__ __qualname____visit_name__r __classcell__rrrrrsrc@eZdZdZdS)TINYINTNrrrrrrrrrrc@s&eZdZddZedZddZdS)_MSDatecC dd}|S)NcS&t|tjkrt|j|j|jS|SNtypedatetimedateyearmonthdayvaluerrrprocessz'_MSDate.bind_processor..processrrdialectrrrrbind_processorz_MSDate.bind_processorz(\d+)-(\d+)-(\d+)cfdd}|S)NcZt|tjr |St|tjr+j|}|std|ftjdd|DS|S)Nz"could not parse %r as a date valuecSg|]}t|pdqSrint.0xrrr z=_MSDate.result_processor..process..) isinstancerrr string_types_regmatch ValueErrorgroupsrmrrrr   z)_MSDate.result_processor..processrrrcoltyperrrrresult_processor  z_MSDate.result_processorN)rrrrrecompilerrrrrrrs rcsFeZdZd fdd ZedddZddZe dZ d d Z Z S) TIMENc s||_tt|dSr)rrrrrrrrkwargsrrrrsz TIME.__init__ilrcfdd}|S)Ncs>t|tjrtjj|}|St|tjr t|}|Sr)rrcombine_TIME__zero_datetimestrrrrrrs   z$TIME.bind_processor..processrrrrrrrzTIME.bind_processorz!(\d+):(\d+):(\d+)(?:\.(\d{0,6}))?cr)Ncr)Nz"could not parse %r as a time valuecSrrrrrrrrrz:TIME.result_processor..process..) rrrr rrrrrrrrrrrz&TIME.result_processor..processrrrrrrrzTIME.result_processorr) rrrrrrrrrrrrrrrrrrs  rc@eZdZddZdS) _DateTimeBasecCr)NcSrrrrrrrrrz-_DateTimeBase.bind_processor..processrrrrrrrz_DateTimeBase.bind_processorN)rrrrrrrrr rc@ eZdZdS) _MSDateTimeNrrrrrrrrrc@r) SMALLDATETIMENrrrrrrrrcs"eZdZdZdfdd ZZS) DATETIME2Nc s tt|jdi|||_dS)Nr)rrrrr)rrrrrrrrs zDATETIME2.__init__rrrrrrrsrc@seZdZdZdddZdS)DATETIMEOFFSETNcKs ||_dSrrrrrrrr  zDATETIMEOFFSET.__init__r)rrrrrrrrrrsrc@r)_UnicodeLiteralcr)Ncs(|dd}jjr|dd}d|S)N'z''%z%%zN'%s')replaceidentifier_preparerZ_double_percentsrrrrrs  z2_UnicodeLiteral.literal_processor..processrrrrrliteral_processors  z!_UnicodeLiteral.literal_processorN)rrrrrrrrr rrc@r) _MSUnicodeNrrrrrrrrc@r)_MSUnicodeTextNrrrrrrrrcs2eZdZdZdZdZdddZfddZZS) TIMESTAMPaBImplement 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` NFcCs ||_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)rrrrrr7s zTIMESTAMP.__init__cs,tt||||jrfdd}|SS)Ncs&|}|durtt|dd}|S)Nhex)rcodecsencodersuper_rrrFsz+TIMESTAMP.result_processor..process)rrrrrrrrrBs  zTIMESTAMP.result_processorF) rrr__doc__rlengthrrrrrrrr#s   rc@eZdZdZdZdS) 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` NrrrrrrrrrrRsrc@r)NTEXTzMMSSQL NTEXT type, for variable-length unicode text up to 2^30 characters.Nrrrrrrjsrc@r) VARBINARYaGThe 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` Nrrrrrrrsrc@r)IMAGENrrrrrrrrc@r)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 Nrrrrrrs rc@r)BITNrrrrrrrrc@r)MONEYNrrrrrrrrc@r) SMALLMONEYNrrrrrrrrc@r)UNIQUEIDENTIFIERNrrrrrrrrc@r) SQL_VARIANTNrrrrrrrrcs$eZdZdZdZfddZZS)TryCastz+Represent a SQL Server TRY_CAST expression.try_castcstt|j|i|dS)aCreate 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)rr r)rargrrrrrszTryCast.__init__)rrrrrrrrrrrr sr z.dialects.mssql.try_castrZbigintZsmallintZtinyintZvarcharZnvarcharcharZnchartextZntextdecimalnumericfloatrZ datetime2Zdatetimeoffsetr) rZ smalldatetimebinaryZ varbinarybitrealimagexml timestampZmoneyZ smallmoneyZuniqueidentifierZ sql_variantc@seZdZd>ddZddZddZdd Zd d Zd d ZddZ ddZ ddZ ddZ ddZ ddZddZddZddZd d!Zd"d#Zd$d%Zd&d'Zd(d)Zd*d+Zd,d-Zd.d/Zd0d1Zd2d3Zd4d5Zd6d7Zd8d9Zd:d;Zd.)getattrrrr^)rspectype_rrrrr_extend s   zMSTypeCompiler._extendcKs$t|dd}|dur dSdd|iS)NrrrzFLOAT(%(precision)s)rrrrrrrrr visit_FLOATs  zMSTypeCompiler.visit_FLOATcKdS)Nrrrrrrrr visit_TINYINT#zMSTypeCompiler.visit_TINYINTcKs|jdur d|jSdS)NzDATETIMEOFFSET(%s)rrr%rrrvisit_DATETIMEOFFSET&s  z#MSTypeCompiler.visit_DATETIMEOFFSETcK t|dd}|durd|SdS)NrrzTIME(%s)rr!r"rrr visit_TIME, zMSTypeCompiler.visit_TIMEcKr$)Nrrr%rrrvisit_TIMESTAMP3r'zMSTypeCompiler.visit_TIMESTAMPcKr$)Nrrr%rrrvisit_ROWVERSION6r'zMSTypeCompiler.visit_ROWVERSIONcKr))Nrrz DATETIME2(%s)rr!r"rrrvisit_DATETIME29r+zMSTypeCompiler.visit_DATETIME2cKr$)Nrrr%rrrvisit_SMALLDATETIME@r'z"MSTypeCompiler.visit_SMALLDATETIMEcKs|j|fi|Sr)visit_NVARCHARr%rrr visit_unicodeCzMSTypeCompiler.visit_unicodecK,|jjr |j|fi|S|j|fi|Sr)rdeprecate_large_types visit_VARCHAR visit_TEXTr%rrr visit_textFzMSTypeCompiler.visit_textcKr3r)rr4r0 visit_NTEXTr%rrrvisit_unicode_textLr8z!MSTypeCompiler.visit_unicode_textcK |d|S)Nrr r%rrrr9R zMSTypeCompiler.visit_NTEXTcKr;)Nrr<r%rrrr6Ur=zMSTypeCompiler.visit_TEXTcK|jd||jpddS)Nrmaxrr rr%rrrr5XzMSTypeCompiler.visit_VARCHARcKr;)Nrr<r%rrr visit_CHAR[r=zMSTypeCompiler.visit_CHARcKr;)Nrr<r%rrr visit_NCHAR^r=zMSTypeCompiler.visit_NCHARcKr>)Nrr?r@rAr%rrrr0arBzMSTypeCompiler.visit_NVARCHARcK0|jjtkr|j|fi|S|j|fi|Sr)rserver_version_infoMS_2008_VERSIONvisit_DATETIMEZ visit_DATEr%rrr visit_dated zMSTypeCompiler.visit_datecKrEr)rrFrGrHr*r%rrr visit_timejrJzMSTypeCompiler.visit_timecKr3r)rr4visit_VARBINARY visit_IMAGEr%rrrvisit_large_binarypr8z!MSTypeCompiler.visit_large_binarycKr$)Nrrr%rrrrMvr'zMSTypeCompiler.visit_IMAGEcKr$)Nrrr%rrr visit_XMLyr'zMSTypeCompiler.visit_XMLcKr>)Nrr?r@rAr%rrrrL|rBzMSTypeCompiler.visit_VARBINARYcKs ||Sr) visit_BITr%rrr visit_booleanrzMSTypeCompiler.visit_booleancKr$)Nrrr%rrrrPr'zMSTypeCompiler.visit_BITcKr$)Nrrr%rrr visit_MONEYr'zMSTypeCompiler.visit_MONEYcKr$)Nrrr%rrrvisit_SMALLMONEYr'zMSTypeCompiler.visit_SMALLMONEYcKr$)Nrrr%rrrvisit_UNIQUEIDENTIFIERr'z%MSTypeCompiler.visit_UNIQUEIDENTIFIERcKr$)Nrrr%rrrvisit_SQL_VARIANTr'z MSTypeCompiler.visit_SQL_VARIANTr)!rrrr r#r&r(r*r,r-r.r/r1r7r:r9r6r5rCrDr0rIrKrNrMrOrLrQrPrRrSrTrUrrrrrs>  rc@sLeZdZdZdZdZdZddZddZddZ d d Z d d Z d dZ dS)MSExecutionContextFNcCs|jjs |j|dS|S)Nr)rZsupports_unicode_statements_encoder)r statementrrr _opt_encodeszMSExecutionContext._opt_encodec Cs|jr~|jjj}|j}|du}|rM|j|jdvpJ|jjjoJ|jjjo5|j|jjjdvp5||jjjdvpJ|jjj oJ|j|jjjvpJ||jjjv|_ nd|_ |jj oc|oc|jj oc|j oc|j |_ |j r|j|j|d|jj|d|dSdSdS)z#Activate IDENTITY_INSERT if needed.NrFzSET IDENTITY_INSERT %s ONr)isinsertcompiledrXr_autoincrement_columnr_Zcompiled_parameters parametersZ_has_multi_parameters_enable_identity_insertinline returningZ executemany_select_lastrowidroot_connection_cursor_executerBrYrr format_table)rZtblZ seq_columnZinsert_has_sequencerrrpre_execs^        *zMSExecutionContext.pre_execc Cs|j}|jr+|jjr||jdd|n ||jdd||jd}t|d|_|j s4|j s4|j r>|j j r>t||_|jrY||j|d|jj|j jjd|dSdS)z#Disable IDENTITY_INSERT if enabled.z$SELECT scope_identity() AS lastrowidrzSELECT @@identity AS lastrowidrSET IDENTITY_INSERT %s OFFN)rbraruse_scope_identityrcrBfetchallr _lastrowidrZisupdateisdeleter[r`rZFullyBufferedResultProxy _result_proxyr^rYrrdrXr)rconnrowrrr post_execsJ  zMSExecutionContext.post_execcCs|jSr)rirrrr get_lastrowidsz MSExecutionContext.get_lastrowidcCsL|jr$z|j|d|jj|jjj WdSt y#YdSwdS)Nrf) r^rBrMrYrrrdr[rXr Exception)rerrrhandle_dbapi_exceptions z)MSExecutionContext.handle_dbapi_exceptioncCs|jr|jSt|Sr)rlrZ ResultProxyrrrrget_result_proxy s z#MSExecutionContext.get_result_proxy) rrrr^rarlrirYrerorprsrtrrrrrVs8& rVcsreZdZdZeejjdddddZfddZ fd d Z d d Z d dZ ddZ ddZddZddZddZddZddZddZdd Zd!d"Zd#d$Zd%d&Ze dOfd(d) Ze fd*d+Ze dPfd-d. Zd/d0Zd1d2Zd3d4Zd5d6Zfd7d8Z d9d:Z!d;d<Z"fd=d>Z#d?d@Z$dAdBZ%dCdDZ&dEdFZ'dGdHZ(dIdJZ)dKdLZ*dMdNZ+Z,S)Q MSSQLCompilerTZ dayofyearweekdayZ millisecond microsecond)ZdoyZdowZ milliseconds microsecondscs i|_tt|j|i|dSr) tablealiasesrrur)rargsrrrrr!szMSSQLCompiler.__init__csfdd}|S)Ncs>|jjr|g|Ri|Sttt|j}||i|Sr)rlegacy_schema_aliasingrrrur)rr rr)rfnrrdecorate&sz.decorater)r|r}rr|r_with_legacy_schema_aliasing%sz*MSSQLCompiler._with_legacy_schema_aliasingcKr$)NZCURRENT_TIMESTAMPrrr|rrrrvisit_now_func/r'zMSSQLCompiler.visit_now_funccKr$)Nz GETDATE()rrrrrvisit_current_date_func2r'z%MSSQLCompiler.visit_current_date_funccKd|j|fi|SNzLEN%sZfunction_argspecrrrrvisit_length_func5rBzMSSQLCompiler.visit_length_funccKrrrrrrrvisit_char_length_func8rBz$MSSQLCompiler.visit_char_length_funccK,d|j|jfi||j|jfi|fS)Nz%s + %srrar{rroperatorrrrrvisit_concat_op_binary;z$MSSQLCompiler.visit_concat_op_binarycKr$)N1rrexprrrrr visit_trueAr'zMSSQLCompiler.visit_truecKr$)N0rrrrr visit_falseDr'zMSSQLCompiler.visit_falsecKr)NzCONTAINS (%s, %s)rrrrrvisit_match_op_binaryGrz#MSSQLCompiler.visit_match_op_binarycKs^d}|jr |d7}|jr |jdus|jr |jdkr |d|j7}|r$|Stjj||fi|S)z- MS-SQL puts TOP, it's version of LIMIT here z DISTINCT NrzTOP %d ) Z _distinct_simple_int_limit_offset_clause_simple_int_offset_offset_limitr SQLCompilerget_select_precolumns)rrrsrrrrMs   z#MSSQLCompiler.get_select_precolumnscC|Srrrrr rrrget_from_hint_textdr'z MSSQLCompiler.get_from_hint_textcCrrrrrrrget_crud_hint_textgr'z MSSQLCompiler.get_crud_hint_textcKr$Nrr)rrrrrr limit_clausejzMSSQLCompiler.limit_clausecKs,d|j|jfi||j|jfi|fS)NzTRY_CAST (%s AS %s))rZclauseZ typeclause)relementrrrrvisit_try_castnrzMSSQLCompiler.visit_try_castcKs(|js|jdus|jdur|jr|jrt|dds|jjs"t ddd|jjD}|j}|j}||d<| }d|_ | t jj|dd d}t d }t d d|jD}|dury|||k|durx||||kn|||k|j|fi|Stjj||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 clausecSsg|]}t|qSr)sql_utilZunwrap_label_reference)relemrrrrsz.MSSQLCompiler.visit_select..Zselect_wraps_forTorder_bymssql_rncSsg|] }|jdkr|qS)r)r_rrrrrs)rZ _limit_clauserrrr_order_by_clauseZclausesr CompileErrorZ _generaterr7rrZ ROW_NUMBERrplabelraliasrrZappend_whereclauserr r visit_select)rrrZ_order_by_clausesrZ offset_clauserZ limitselectrrrrtsZ     zMSSQLCompiler.visit_selectFc sd||us|rtt|j|fi|S||}|dur&|j|fd|i|Stt|j|fi|SN mssql_aliased)rru visit_table_schema_aliased_tabler)rrriscrudrrrrrrs  zMSSQLCompiler.visit_tablec s"|j|d<tt|j|fi|Sr)originalrru visit_alias)rrrrrrrs zMSSQLCompiler.visit_aliasNc s|jdur |js |jr|r>||j}|dur>t||}|dur2||j|j||j|jf|j t t |j |fi|St t |j |fd|i|S)Nadd_to_result_map) rrjrk is_subqueryrrZ_corresponding_column_or_errornamer_rrru visit_column)rr7rrtZ convertedrrrrs6    zMSSQLCompiler.visit_columncCs6t|dddur||jvr||j|<|j|SdS)Nr)rryr)rrrrrrs   z#MSSQLCompiler._schema_aliased_tablecKs.|j|j|j}d||j|jfi|fS)NzDATEPART(%s, %s)) extract_mapgetfieldrr)rextractrrrrr visit_extractszMSSQLCompiler.visit_extractcCd|j|S)NzSAVE TRANSACTION %spreparerZformat_savepointrZsavepoint_stmtrrrvisit_savepointzMSSQLCompiler.visit_savepointcCr)NzROLLBACK TRANSACTION %srrrrrvisit_rollback_to_savepointrz)MSSQLCompiler.visit_rollback_to_savepointc sbt|jtjr%|jtjkr%t|jtjs%|jt|j|j|jfi|St t |j |fi|S)z]Move bind parameters to the right-hand side of an operator, where possible. ) rrarZ BindParameterreqr{rZBinaryExpressionrru visit_binary)rrrrrrrs    zMSSQLCompiler.visit_binarycsXjsjr |jd}n|jd}t|fddt|D}dd|S)NZinsertedZdeletedc s$g|]}d|ddiqS)NTF)Z_label_select_columntraverseradapterrrrr s z2MSSQLCompiler.returning_clause..zOUTPUT , ) rZrjrrrZ ClauseAdapterrZ_select_iterablesr^)rstmtZreturning_colstargetcolumnsrrrreturning_clauses    zMSSQLCompiler.returning_clausecCr$)NZWITHr)r recursiverrrget_cte_preambleszMSSQLCompiler.get_cte_preamblecs*t|tjr |dStt||||Sr)rrFunctionrrrulabel_select_column)rrr7asfromrrrrs   z!MSSQLCompiler.label_select_columncCr$rr)rrrrrfor_update_clause$szMSSQLCompiler.for_update_clausecKs6|r |js dS|j|jfi|}|rd|SdS)Nrz ORDER BY )rrrr)rrrrrrrorder_by_clause)s zMSSQLCompiler.order_by_clausec &ddfdd|g|DS)aRender 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 rc3(|]}|jfddVqdST)rZ fromhintsNZ_compiler_dispatchrr from_hintsrrrr B  z3MSSQLCompiler.update_from_clause..r^)rZ update_stmt from_table extra_fromsrrrrrupdate_from_clause8s  z MSSQLCompiler.update_from_clausecCsd}|rd}|j|dd|dS)z=If we have extra froms make sure we render any alias as hint.FT)rrashintr)r delete_stmtrrrrrrdelete_table_clauseGs z!MSSQLCompiler.delete_table_clausec r)zjRender the DELETE .. FROM clause specific to MSSQL. Yes, it has the FROM keyword twice. rrc3rrrrrrrrXrz9MSSQLCompiler.delete_extra_from_clause..r)rrrrrrrrrdelete_extra_from_clausePs z&MSSQLCompiler.delete_extra_from_clausecCr$)NzSELECT 1 WHERE 1!=1r)rrrrrvisit_empty_set_expr]r'z"MSSQLCompiler.visit_empty_set_exprcKd||j||jfS)Nz*NOT EXISTS (SELECT %s INTERSECT SELECT %s)rrrrrvisit_is_distinct_from_binary`  z+MSSQLCompiler.visit_is_distinct_from_binarycKr)Nz&EXISTS (SELECT %s INTERSECT SELECT %s)rrrrr visit_isnot_distinct_from_binaryfrz.MSSQLCompiler.visit_isnot_distinct_from_binary)FFr)-rrrZreturning_precedes_valuesr Z update_copyr rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrus`  :     rucs4eZdZdZdZddZddZfddZZS) 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. TcK4d|d<d|j|jfi||j|jfi|fS)NT literal_bindsz%s IN %srrrrrvisit_in_op_binaryy z&MSSQLStrictCompiler.visit_in_op_binarycKr)NTrz %s NOT IN %srrrrrvisit_notin_op_binaryrz)MSSQLStrictCompiler.visit_notin_op_binarycs2tt|tjrdt|dStt|||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. r) issubclassrrrrrrrender_literal_value)rrrrrrrs   z(MSSQLStrictCompiler.render_literal_value) rrrrZansi_bind_rulesrrrrrrrrrms rc@s>eZdZddZdddZddZdd Zd d Zd d ZdS) MSDDLCompilercKs|j|}|jdur|d||j7}n|d|jjj|j|d7}|jdurI|jr;|js;t |j t j s;|j dur@|d7}n |jdurI|d7}|jdurStdt |j t j r|j jdusl|j jdusl||jjurqtd|j jdkrzd}n|j jpd }|d ||j jpd f7}|S||jjus|j dur|jd d }|jd d }|d ||f7}|S||}|dur|d|7}|S)Nr)Ztype_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.rrz IDENTITY(%s,%s)mssqlidentity_startidentity_incrementz DEFAULT )rZ format_columncomputedrr type_compilerrnullableZ primary_keyrr sa_schemaSequence autoincrementrrrstart incrementr\r warn_deprecateddialect_optionsZget_column_default_string)rr7rZcolspecrrr rrrget_column_specifications\                  z&MSDDLCompiler.get_column_specificationFc s|jjd}jr|d7}jdd}|dur*|r&|d7}n|d7}|dj|djd fd d j Df7}jdd rlfd djdd D}|dd fdd|D7}jdd}|durj j |ddd}|d|7}|S)NzCREATE UNIQUE rr6 CLUSTERED NONCLUSTERED zINDEX %s ON %s (%s)include_schemarc3s"|] }jj|dddVqdS)FTZ include_tablerN) sql_compilerr)rrrrrrs z3MSDDLCompiler.visit_create_index..includecs(g|]}t|tjrjj|n|qSr)rr rrr)rcol)rZrrrs  z4MSDDLCompiler.visit_create_index..z INCLUDE (%s)csg|]}|jqSr)quoterr)rrrrrrFTrz WHERE ) rZ_verify_index_tablerrr_prepared_index_namerdrr^Z expressionsrr)rr=r r r6Z inclusions whereclauseZwhere_compiledr)rZrrrvisit_create_indexs@       z MSDDLCompiler.visit_create_indexcCs$d|j|jdd|j|jjfS)Nz DROP INDEX %s ON %sFr )rrrrdr)rrFrrrvisit_drop_indexszMSDDLCompiler.visit_drop_indexcst|dkrdSd}|jdur|dj|7}|d7}|jdd}|dur3|r/|d7}n|d7}|d d fd d |D7}||7}|S) NrrCONSTRAINT %s z PRIMARY KEY rr6r r rrc3|] }j|jVqdSrrrrrrrrr, z=MSDDLCompiler.visit_primary_key_constraint..lenrrZformat_constraintrr^Zdefine_constraint_deferrability)rr9r r6rrrvisit_primary_key_constraints$     z*MSDDLCompiler.visit_primary_key_constraintcst|dkrdSd}|jdurj|}|dur|d|7}|d7}|jdd}|dur9|r5|d7}n|d7}|d d fd d |D7}||7}|S) Nrrrr rr6r r rrc3rrrrrrrrCrz8MSDDLCompiler.visit_unique_constraint..r)rr9r Zformatted_namer6rrrvisit_unique_constraint2s$      z%MSDDLCompiler.visit_unique_constraintcCs.d|jj|jddd}|jdur|d7}|S)NzAS (%s)FTrz PERSISTED)rrsqltext persisted)r generatedr rrrvisit_computed_columnIs  z#MSDDLCompiler.visit_computed_columnNr) rrrrrrrrr"rrrrrs F2 rcs:eZdZeZfddZddZddZd dd ZZ S) MSIdentifierPreparercstt|j|dddddS)N[]F)Z initial_quoteZ final_quoteZquote_case_sensitive_collations)rr#r)rrrrrrVs  zMSIdentifierPreparer.__init__cC |ddS)Nr%]]rrrrrr_escape_identifier^r=z'MSIdentifierPreparer._escape_identifiercCr&)Nr'r%r(r)rrr_unescape_identifierar=z)MSIdentifierPreparer._unescape_identifierNcCsX|dur tdt|\}}|rd||||f}|S|r(||}|Sd}|S)z'Prepare a quoted table and schema name.NzThe IdentifierPreparer.quote_schema.force parameter is deprecated and will be removed in a future release. This flag has no effect on the behavior of the IdentifierPreparer.quote method; please refer to quoted_name().%s.%sr)r r_schema_elementsr)rrforcedbnameownerresultrrr quote_schemads  z!MSIdentifierPreparer.quote_schemar) rrrRESERVED_WORDSZreserved_wordsrr*r+r2rrrrrr#Ss  r#cdfdd }t|S)Nc s,t||\}}t|||||||fi|Sr_owner_plus_db _switch_db)r connectionrrr/r0r~rrwraps z$_db_plus_owner_listing..wraprrr|r9rr~r_db_plus_owner_listing~s r;cr4)Nc s.t||\}}t||||||||f i|Srr5)rr8 tablenamerrr/r0r~rrr9s z_db_plus_owner..wraprrr:rr~r_db_plus_owners r=c Os|r|d}||kr|d|jj|z||i|W|r2||kr3|d|jj|SSS|rG||krH|d|jj|www)Nzselect db_name()zuse %s)scalarrMrrr)r/r8r|r rZ current_dbrrrr7s*    r7cCs&|sd|jfSd|vrt|Sd|fS)N.)default_schema_namer-)rrrrrr6s  r6cCsJt|tr |jr d|fS|tvrt|Sg}d}d}d}td|D]3}|s'q"|dkr0d}d}q"|dkr7d}q"|sQ|dkrQ|rG|d|n||d}d}q"||7}q"|r]||t|d krd|d d |d }}t d |d d rt|dd }n| d d}nt|rd|d }}nd\}}||ft|<||fS)NrFz (\[|\]|\.)r$Tr%r?z[%s]rrz .*\].*\[.*r)NN) rrr_memoized_schemarsplitappendrr^rlstriprstrip)rpushsymbolZbracketZ has_bracketstokenr/r0rrrr-sF       r-c seZdZdZdZdZeZdZdZ dZ e j e e jee jee jee jeiZejjdejfgZeZdZdZdZ dZ!dZ"dZ#e$Z%e&Z'e(Z)e*Z+e,j-dd ife,j.dd ife,j/d d d d fe,j0d d d fgZ1   d4fd d Z2fddZ3ddZ4e5gdZ6ddZ7ddZ8fddZ9ddZ:ddZ;ddZd"d#Z?e@jAd$d%ZBe@jAeCd&d'ZDe@jAeCd(d)ZEe@jAe>d*d+ZFe@jAe>d,d-ZGe@jAe>d.d/ZHe@jAe>d0d1ZIe@jAe>d2d3ZJZKS)5 MSDialectrTFdbor{rr6N)r6rrr)rrc sFt|pd|_||_||_||_||_tt|jdi|||_ dS)Nrr) r query_timeout schema_namergr4r{rrKrisolation_level)rrNrgrOrPr4r{optsrrrr" s  zMSDialect.__init__cs |dtt|||dS)Nz$IF @@TRANCOUNT = 0 BEGIN TRANSACTION)rMrrK do_savepointrr8rrrrrR7 s zMSDialect.do_savepointcCsdSrrrSrrrdo_release_savepoint< rzMSDialect.do_release_savepoint)Z SERIALIZABLEzREAD UNCOMMITTEDzREAD COMMITTEDzREPEATABLE READSNAPSHOTcCsj|dd}||jvrtd||jd|jf|}|d|||dkr3| dSdS)N_rzLInvalid value '%s' for isolation_level. Valid isolation levels for %s are %srz"SET TRANSACTION ISOLATION LEVEL %srU) r_isolation_lookupr ArgumentErrorrr^rBrMr5r8)rr8levelrBrrrset_isolation_levelJ s   zMSDialect.set_isolation_levelc Cs|jtkr tdd}d}|D]A}|}z6z|d||d}Wn|jjy@}z |}WYd}~W|qd}~ww| W|S|wt d||ftd||f)Nz4Can't fetch isolation level prior to SQL Server 2005)zsys.dm_exec_sessionszsys.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 rzQCould not fetch transaction isolation level, tried views: %s; final error was: %szgCan't fetch isolation level on this particular SQL Server version. tried views: %s; final error was: %s) rFMS_2005_VERSIONNotImplementedErrorrBrMfetchoneZdbapiErrorr5upperr warn)rr8Z last_errorZviewsrrBvalerrrrrget_isolation_levelX sB    zMSDialect.get_isolation_levelcs&tt|||||dSr)rrK initialize_setup_version_attributes_setup_supports_nvarchar_maxrr8rrrrd szMSDialect.initializecsjdur fdd}|SdS)Ncs|jdSr)rZrP)rmrrrconnect r2z%MSDialect.on_connect..connect)rP)rrhrrr on_connect s  zMSDialect.on_connectcCs|jdttddvrtdddd|jD|jtkr)d|jvr)d |_|jt kr1d |_ |j dur>|jt k|_ dSdS) Nrr'z[Unrecognized server version info '%s'. Some SQL Server features may not function properly.r?css|]}t|VqdSr)rrrrrr sz6MSDialect._setup_version_attributes..implicit_returningT) rFlistranger r`r^r[__dict__rkrGZsupports_multivalues_insertr4MS_2012_VERSIONrrrrre s    z#MSDialect._setup_version_attributescCs<z |tdWntjyd|_YdSwd|_dS)Nz0SELECT CAST('test max support' AS NVARCHAR(max))FT)r>rr rZ DBAPIError_supports_nvarchar_maxrgrrrrf s  z&MSDialect._setup_supports_nvarchar_maxcCs>|jtkr|jStd}||}|durt|ddS|jS)NzSELECT schema_name()TrB)rFr[rOrr r>r)rr8queryr@rrr_get_default_schema_name s    z"MSDialect._get_default_schema_namec CsNtj}|jj|k}|rt||jj|k}t|g|}||} | duSr) ischemarr table_namerand_ table_schemarrMfirst) rr8r<r/r0rrrrrrrr has_table s    zMSDialect.has_tablecKs6tjtjjjgtjjjgd}dd||D}|S)NrcSg|]}|dqSrrrrrrrr z.MSDialect.get_schema_names..)rrrsZschematarrOrM)rr8rrZ schema_namesrrrget_schema_names s   zMSDialect.get_schema_namesc KRtj}tj|jjgt|jj|k|jjdk|jjgd}dd| |D}|S)Nz BASE TABLErcSryrrrzrrrr r|z-MSDialect.get_table_names.. rstablesrrrrtrurvZ table_typerM) rr8r/r0rrrrZ table_namesrrrget_table_names s  zMSDialect.get_table_namesc Kr~)NZVIEWrcSryrrrzrrrr r|z,MSDialect.get_view_names..r) rr8r/r0rrrrZ view_namesrrrget_view_names szMSDialect.get_view_namesc Ks|jtkrgS|tdtd|ttd|tj t d}i}|D]} | d| ddkgd|| d <q+|td td|ttd|tj t d}|D]} | d |vru|| d d  | dq`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 != 0Ztabnameschname)rrZ is_uniquer)rr column_namesZindex_idaRselect 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)rFr[rMrr  bindparams bindparamrs CoerceUnicodersqltypesUnicoderErlr) rr8r<r/r0rrrpZindexesrnrrr get_indexes sF      zMSDialect.get_indexesc KsH|tdtd|ttd|t}|r"|}|SdS)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)rMrr rrrsrr>) rr8rr/r0rrrZview_defrrrget_view_definition, szMSDialect.get_view_definitionc& Kstj}tj}|r0t|jj|k|jj|k} d||f} |jjd|jj} |jjt | k} n|jj|k} |} |jjt |jjk} t| |jj |jj k} |j || dd} |j r_|jj}n t|jjtd}tj|||jjg| | |jjgd}||}g} |}|durn||jj }||jj}||jjdk}||jj}||jj}||jj}||jj}||jj}||}||jj}|j|d}i}|tt t!t"t#t$t%t&t'j(f vr|dkrd}||d <|r||d <|durt)*d ||ft'j+}nt,|t'j-r||d <t,|t'j.s||d <|di|}||||dd}|dur5|dur5||d|d<|/|qi} |D] }!|!| |!d<q?|t0d||d}"d}# |"}|durbn(|d|d}$}%|%1dr|$| vr|$}#d| |$d<ddd| |$d<nqX|"2|#dur|j3t4krd||f} |d| | f}"|"5}|dur|ddur| |#d6t7|dt7|dd|S)Nr,r?T)ZonclauseZisouteri)Zfrom_objrZYESrArrz*Did not recognize type '%s' of column '%s'rrscaleF)rrrr r)rr rrzAsp_columns @table_name = :table_name, @table_owner = :table_owner)rtZ table_ownerrrWrr)Zmssql_identity_startZmssql_identity_incrementrz)select ident_seed('%s'), ident_incr('%s')rr)8rsrZcomputed_columnsrrurrtrvZ object_idr column_namerr^rp definitioncastrr is_persistedordinal_positionrMr]Z data_typeZ is_nullableZcharacter_maximum_lengthZnumeric_precisionZ numeric_scaleZcolumn_defaultZcollation_name ischema_namesrMSStringMSChar MSNVarcharMSNCharMSTextMSNTextMSBinary MSVarBinaryr LargeBinaryr r`ZNULLTYPErZNumericFloatrEr endswithr5rFr[rwrr)&rr8r<r/r0rrrZ computed_colsrZtable_fullnameZ full_nameZjoin_onr^Zcomputed_definitionrrcolsrnrrrZcharlenZ numericprecZ numericscaler rrrrrZcdictZcolmaprrBZicZcol_name type_namerrr get_columnsD s                   A       zMSDialect.get_columnsc Ksg}tj}tjd} t| jj|jj| jj gt |jj | jj k|jj | jj k| jj |k| jj |k |jj | jj} || } d} | D]} d| |jjjvrb|| d| durb| | jj j} qE|| dS)NCZPRIMARYr)constrained_columnsr)rs constraintskey_constraintsrrrrrZconstraint_typeconstraint_namerurvrtrrrMrrE)rr8r<r/r0rrZpkeysZTCrrrrrnrrrget_pk_constraint s.     zMSDialect.get_pk_constraintc Kstj}tjd}tjd} tj|jj| jj| jj | jj|jj |jj |jj |jj gt|jj |k|jj|k|jj|jjk|jj |jj k| jj |jjk| jj|jjk|jj| jjk|jj | jjgd} g} dd} t| } || D]C} | \}}}}}}}}| |}||d<|ds||d<|dus||kr|r|d|}||d <|d |d }}||||qvt| S) NrRrcSsdgddgdS)N)rrreferred_schemareferred_tablereferred_columnsrrrrrfkey_rec s z,MSDialect.get_foreign_keys..fkey_recrrr?rrr)rsZref_constraintsrrrrrrrvrtrZ match_optionZ update_ruleZ delete_ruleruZconstraint_schemaZunique_constraint_nameZunique_constraint_schemarr defaultdictrMrhrErlr)rr8r<r/r0rrZRRrrrZfkeysrr{ZscolZrschemaZrtblZrcolZrfknmZfkmatchZfkupruleZ fkdelruleZrecZ local_colsZ remote_colsrrrget_foreign_keys sV          zMSDialect.get_foreign_keys)NTrMNNF)LrrrrZsupports_default_valuesZsupports_empty_insertrVZexecution_ctx_clsrgZmax_identifier_lengthrOrDateTimerDaterZTimerrr UnicodeTextrZcolspecsr DefaultDialectZengine_config_typesrr ZasboolrZsupports_native_booleanZ#non_native_boolean_check_constraintZsupports_unicode_bindsZpostfetch_lastrowidrprFruZstatement_compilerrZ ddl_compilerrrr#rrZPrimaryKeyConstraintZUniqueConstraintIndexColumnZconstruct_argumentsrrRrTrrWrZrcrdrirerfrrr=rxr cacher}r;rrrrrrrrrrrrrKs       0         5   rK)rrrrrrrrsrrrrrr rr r r r rrrrrrrrrrrrrrrrrrr Zutil.langhelpersr!ZMS_2016_VERSIONZMS_2014_VERSIONrorGr[ZMS_2000_VERSIONrr3rIntegerrrrrZ_MSTimeobjectrrrrrZ TypeEnginerrrrrrZ_BinaryrrrrrrTextrrrrrrelementsZCastr r Z MSDateTimeZMSDateZMSRealZ MSTinyIntegerZMSTimeZMSSmallDateTimeZ MSDateTime2ZMSDateTimeOffsetrrrrrrrrZMSImageZMSBitZMSMoneyZ MSSmallMoneyZMSUniqueIdentifierZ MSVariantrZGenericTypeCompilerrZDefaultExecutionContextrVrrurZ DDLCompilerrZIdentifierPreparerr#r;r=r7r6ZLRUCacherCr-rrKrrrrsJ"                              ;  *  /      " [/8+ 7