delta/python-packages/sqlalchemy.git/test/dialect/mssql/test_compiler.py, branch pr/188

- Added a new dialect flag to the MSSQL dialect

2015-05-25T01:02:29+00:00

``legacy_schema_aliasing`` which when set to False will disable a
very old and obsolete behavior, that of the compiler's
attempt to turn all schema-qualified table names into alias names,
to work around old and no longer locatable issues where SQL
server could not parse a multi-part identifier name in all
circumstances.   The behavior prevented more
sophisticated statements from working correctly, including those which
use hints, as well as CRUD statements that embed correlated SELECT
statements.  Rather than continue to repair the feature to work
with more complex statements, it's better to just disable it
as it should no longer be needed for any modern SQL server
version.  The flag defaults to True for the 1.0.x series, leaving
current behavior unchanged for this version series.  In the 1.1
series, it will default to False.  For the 1.0 series,
when not set to either value explicitly, a warning is emitted
when a schema-qualified table is first used in a statement, which
suggests that the flag be set to False for all modern SQL Server
versions.
fixes #3424
fixes #3430

- autopep8

2015-05-24T21:07:54+00:00

- fix some more result_map calls

2015-03-08T18:16:59+00:00

- the change for #918 was of course not nearly that simple.

2015-03-08T04:03:27+00:00

The "wrapping" employed by the mssql and oracle dialects using the
"iswrapper" argument was not being used intelligently by the compiler,
and the result map was being written incorrectly, using
*more* columns in the result map than were actually returned by
the statement, due to "row number" columns that are inside the
subquery.   The compiler now writes out result map on the
"top level" select in all cases
fully, and for the mssql/oracle wrapping case extracts out
the "proxied" columns in a second step, which only includes
those columns that are proxied outwards to the top level.

This change might have implications for 3rd party dialects that
might be imitating oracle's approach.   They can safely continue
to use the "iswrapper" kw which is now ignored, but they may
need to also add the _select_wraps argument as well.

- more tests, including backend tests

2014-05-16T19:33:39+00:00

- implement for SQL server, use window functions when simple limit/offset not available

Support mssql_clustered option on UniqueConstraint (plus docs and test)

2014-01-16T21:46:16+00:00

Remove support for mssql_clustered on Table

2014-01-16T21:38:31+00:00

Support mssql_clustered option in mssql dialect for both Table and PrimaryKeyConstraint

2014-01-13T23:44:05+00:00

- changelog + test for pullreq #7, MSSQL dialect for DROP INDEX

2013-12-05T23:36:59+00:00

- Fixed bug in default compiler plus those of postgresql, mysql, and

2013-10-13T00:04:55+00:00

mssql to ensure that any literal SQL expression values are
rendered directly as literals, instead of as bound parameters,
within a CREATE INDEX statement. [ticket:2742]
- don't need expression_as_ddl(); literal_binds and include_table
take care of this functionality.