| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
like this
(cherry picked from commit 0e7904e730c3d2b0d3a394ad60010158ee29050c)
|
| |
|
|
|
|
|
| |
because we never log in on the ts1/ts2. races against other runs
and erases their DBs
(cherry picked from commit 3f1f1895ac99963da1a989c69c2dce59ae916ffc)
|
| | |
|
| |
|
|
| |
we dont get file conflicts, cherry-pick from 5bb2536cc57c55c7d8c5901b5b622d18a9a6c646
|
| |
|
|
|
|
|
|
|
|
| |
connections at all,
yet cx_Oracle still has open sessions that cannot be killed until process dies.
Oracle wins! Add a completely separate DB reaper script that runs
after py.test is done.
(cherry picked from commit 11a8440bc43aa9f7eb6f2cb7b7f43e0cf6680f41)
|
| |
|
|
| |
(cherry picked from commit 93c5328e66d8491e73027f6e789df2255c4fa767)
|
| |
|
|
| |
(cherry picked from commit c01d11907cbc98ddefe323c6115bc954b908f101)
|
| |
|
|
|
|
| |
on database use
(cherry picked from commit c8b3d4ed3f2638599fc73486cf0f724fa033a638)
|
| |
|
|
|
| |
option for it. keep it local to production of config so values don't
leak in a multi --db situation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
``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
|
| | |
|
| | |
|
|
|
- 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
|