delta/python-packages/sqlalchemy.git/test/dialect, branch workflow_test_aiosqlite

ensure pysqlite dialect enumerates correct isolation levels

2021-08-30T15:35:10+00:00

Fixed bug where the error message for SQLite invalid isolation level on the
pysqlite driver would fail to indicate that "AUTOCOMMIT" is one of the
valid isolation levels.

Change-Id: Icbceab9a28af6a560859761fa92320b5473269a9
References: #6959

Qualify server version call in PostgreSQL

2021-08-24T20:37:08+00:00

Fixes: #6912
Closes: #6920
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/6920
Pull-request-sha: 79af75dfddef25435afd9623698354d280d7c879

Change-Id: Ib6b472452f978378d9f511d17a26988323a89459

fix linter JOIN logic; fix PostgreSQL ARRAY op comparison

2021-08-16T03:14:59+00:00

Adjusted the "from linter" warning feature to accommodate for a chain of
joins more than one level deep where the ON clauses don't explicitly match
up the targets, such as an expression such as "ON TRUE". This mode of use
is intended to cancel the cartesian product warning simply by the fact that
there's a JOIN from "a to b", which was not working for the case where the
chain of joins had more than one element.

this incurs a bit more compiler overhead that comes out in profiling
but is not extensive.

Added the "is_comparison" flag to the PostgreSQL "overlaps",
"contained_by", "contains" operators, so that they work in relevant ORM
contexts as well as in conjunction with the "from linter" feature.

Fixes: #6886
Change-Id: I078dc3fe6d4f7871ffe4ebac3e71e62f3f213d12

Merge "dont qualify literal_binds with literal_execute"

2021-08-07T18:56:11+00:00

dont qualify literal_binds with literal_execute

2021-08-07T16:13:57+00:00

this appears to be unnecessary and prevents end-user
literal_binds case from working.

Fixed issue where the ``literal_binds`` compiler flag, as used externally
to render bound parameters inline, would fail to work when used with a
certain class of parameters known as "literal_execute", which covers things
like LIMIT and OFFSET values for dialects where the drivers don't allow a
bound parameter, such as SQL Server's "TOP" clause.  The issue locally
seemed to affect only the MSSQL dialect.

Fixes: #6863
Change-Id: Ia74cff5b0107b129a11b9b965883552b2962e449

Modernize tests - dml_values

2021-07-26T20:00:53+00:00

Change-Id: Ida86ed40c43d91813151621b847376976773a5f9

Modernize tests - dml_whereclause

2021-07-26T16:08:30+00:00

Fixed issue where the unit of work would internally use a 2.0-deprecated
SQL expression form, emitting a deprecation warning when SQLALCHEMY_WARN_20
were enabled.

Fixes: #6812
Change-Id: I0a031e728527a1c3382848b6ddc793939362b128

Modernize tests - legacy_select

2021-07-21T20:14:43+00:00

Change-Id: I04057cc3d3f93de60b02999803e2ba6a23cdf68d

Merge "Modernize tests - union"

2021-07-13T19:17:28+00:00

Merge "Extract format_constraint truncation rules to ON CONFLICT"

2021-07-13T15:09:05+00:00