delta/python-packages/sqlalchemy.git/lib/sqlalchemy/testing/provision.py, branch pr/202 github.com: zzzeek/sqlalchemy.git - db_opts doesn't need to be a global since we no longer have any global 2015-07-17T15:09:29+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-07-17T15:09:29+00:00 c8f38dff1143585226cd79865a6144d16ee0ba18 option for it. keep it local to production of config so values don't leak in a multi --db situation. 
option for it.  keep it local to production of config so values don't
leak in a multi --db situation.
- Added a new dialect flag to the MSSQL dialect 2015-05-25T01:02:29+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-05-25T01:02:29+00:00 9157911013532e081f9ec6e29e7a4c271438f8ab ``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 
``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
cleanup exception handling - use new exception hierarchy (since python 2.5) 2014-10-02T20:00:31+00:00 ndparker ndparker@users.noreply.github.com 2014-10-02T20:00:31+00:00 690532131d8ce8250c62f1d3e27405902df03e70 






improve exception vs. exit handling
2014-09-23T21:28:11+00:00

ndparker
ndparker@users.noreply.github.com

2014-09-23T21:28:11+00:00

ce52dd9e3b71f2074d7821fe62803d4e0eefe512












- remove some crufty old testing options
2014-09-15T01:41:13+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-09-15T01:41:13+00:00

d7498cf4adb8ef9f35d1efa6dc747ac9eb489e60

- reestablish the "bootstrap" system of loading the test runners
in testing/plugin; using the updated approach we just came up with for
alembic.  Coverage should be fixed now when running either py.test or
nose. fixes #3196
- upgrade tox.ini and start using a .coveragerc file





- reestablish the "bootstrap" system of loading the test runners
in testing/plugin; using the updated approach we just came up with for
alembic.  Coverage should be fixed now when running either py.test or
nose. fixes #3196
- upgrade tox.ini and start using a .coveragerc file