delta/python-packages/sqlalchemy.git/test/sql/test_operators.py, branch master

Remove deprecated dialects and drivers

2021-10-31T16:31:56+00:00

Fixes: #7258
Change-Id: I3577f665eca04f2632b69bcb090f0a4ec9271db9

repair any_() / all_() "implicit flip" behavior for None

2021-10-04T16:04:11+00:00

Fixed an inconsistency in the any_() / all_() functions / methods where the
special behavior these functions have of "flipping" the expression such
that the "ANY" / "ALL" expression is always on the right side would not
function if the comparison were against the None value, that is,
"column.any_() == None" should produce the same SQL expression as "null()
== column.any_()". Added more docs to clarify this as well, plus mentions
that any_() / all_() generally supersede the ARRAY version "any()" /
"all()".

Fixes: #7140
Change-Id: Ia5d55414ba40eb3fbda3598931fdd24c9b4a4411

Modernize tests - select(whereclause)

2021-07-04T21:56:40+00:00

Change-Id: I306cfbea9920b35100e3087dcc21d7ffa6c39c55

Update black flak8 and zimports

2021-05-12T20:10:19+00:00

Change-Id: I488c9557eda390e4a88319affd4c8813ee274f80

set bindparam.expanding in coercion again

2021-05-11T03:42:41+00:00

Adjusted the logic added as part of :ticket:`6397` in 1.4.12 so that
internal mutation of the :class:`.BindParameter` object occurs within the
clause construction phase as it did before, rather than in the compilation
phase. In the latter case, the mutation still produced side effects against
the incoming construct and additionally could potentially interfere with
other internal mutation routines.

In order to solve the issue of the correct operator being present
on the BindParameter.expand_op, we necessarily have to expand the
BinaryExpression._negate() routine to flip the operator on the
BindParameter also.

Fixes: #6460
Change-Id: I1e53a9aeee4de4fc11af51d7593431532731561b

Merge "don't cache TypeDecorator by default"

2021-05-06T21:12:48+00:00

don't cache TypeDecorator by default

2021-05-06T17:57:43+00:00

The :class:`.TypeDecorator` class will now emit a warning when used in SQL
compilation with caching unless the ``.cache_ok`` flag is set to ``True``
or ``False``. ``.cache_ok`` indicates that all the parameters passed to the
object are safe to be used as a cache key, ``False`` means they are not.

Fixes: #6436
Change-Id: Ib1bb7dc4b124e38521d615c2e2e691e4915594fb

Parenthesize for empty not in

2021-05-05T13:54:46+00:00

Fixed regression caused by the "empty in" change just made in
:ticket:`6397` 1.4.12 where the expression needs to be parenthesized for
the "not in" use case, otherwise the condition will interfere with the
other filtering criteria.

also amends StrSQLCompiler to use the newer "empty IN" style for
its compilation process.

Fixes: #6428
Change-Id: I182a552fc0d3065a9e38c0f4ece2deb143735c36

Fit literal compile of empty in on a tuple

2021-04-16T20:28:16+00:00

Fixed regression where an empty in statement on a tuple would result
in an error when compiled with the option ``literal_binds=True``.

Fixes: #6290
Change-Id: Ic0dff8f4a874cccdb201b6d9dcd3c2e7b7884cbb

Infer types in BindParameter when expanding=True

2021-04-08T14:29:08+00:00

Enhanced the "expanding" feature used for :meth:`_sql.ColumnOperators.in_`
operations to infer the type of expression from the right hand list of
elements, if the left hand side does not have any explicit type set up.
This allows the expression to support stringification among other things.
In 1.3, "expanding" was not automatically used for
:meth:`_sql.ColumnOperators.in_` expressions, so in that sense this change
fixes a behavioral regression.

Fixes: #6222
Change-Id: Icdfda1e2c226a21896cafd6d8f251547794451c2