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

- update the flake8 rules again

2014-07-18T21:40:58+00:00

- apply autopep8 + manual fixes to most of test/sql/

- Fixed a bug within the custom operator plus :meth:`.TypeEngine.with_variant`

2014-06-27T20:08:42+00:00

system, whereby using a :class:`.TypeDecorator` in conjunction with
variant would fail with an MRO error when a comparison operator was used.
fixes #3102

- Fixed bug where the :meth:`.Operators.and`,

2014-05-24T18:35:28+00:00

:meth:`.Operators.__or__` and :meth:`.Operators.__invert__`
operator overload methods could not be overridden within a custom
:class:`.TypeEngine.Comparator` implementation.
fixes #3012

- Fixes to the newly enhanced boolean coercion in :ticket:`2804` where

2014-04-01T17:03:52+00:00

the new rules for "where" and "having" woudn't take effect for the
"whereclause" and "having" kw arguments of the :func:`.select` construct,
which is also what :class:`.Query` uses so wasn't working in the
ORM either. fixes #3013 re: #2804

- Added new flag :paramref:`.expression.between.symmetric`, when set to True

2014-03-31T01:20:20+00:00

renders "BETWEEN SYMMETRIC".  Also added a new negation operator
"notbetween_op", which now allows an expression like ``~col.between(x, y)``
to render as "col NOT BETWEEN x AND y", rather than a parentheiszed NOT
string.  fixes #2990

- Fixed bug in :func:`.tuple_` construct where the "type" of essentially

2014-02-28T00:54:49+00:00

the first SQL expression would be applied as the "comparison type"
to a compared tuple value; this has the effect in some cases of an
inappropriate "type coersion" occurring, such as when a tuple that
has a mix of String and Binary values improperly coerces target
values to Binary even though that's not what they are on the left
side.  :func:`.tuple_` now expects heterogeneous types within its
list of values.
fixes #2977

- Fixed bug where :meth:`.in_()` would go into an endless loop if

2014-02-13T20:19:12+00:00

erroneously passed a column expression whose comparator included
the ``__getitem__()`` method, such as a column that uses the
:class:`.postgresql.ARRAY` type. [ticket:2957]

- Added a new parameter :paramref:`.Operators.op.is_comparison`. This

2014-02-01T00:14:08+00:00

flag allows a custom op from :meth:`.Operators.op` to be considered
as a "comparison" operator, thus usable for custom
:paramref:`.relationship.primaryjoin` conditions.

- The precedence rules for the :meth:`.ColumnOperators.collate` operator

2013-12-06T00:03:31+00:00

have been modified, such that the COLLATE operator is now of lower
precedence than the comparison operators.  This has the effect that
a COLLATE applied to a comparison will not render parenthesis
around the comparison, which is not parsed by backends such as
MSSQL.  The change is backwards incompatible for those setups that
were working around the issue by applying :meth:`.Operators.collate`
to an individual element of the comparison expression,
rather than the comparison expression as a whole. [ticket:2879]

An overhaul of expression handling for special symbols particularly

2013-10-23T21:44:52+00:00

with conjunctions, e.g.
``None`` :func:`.expression.null` :func:`.expression.true`
:func:`.expression.false`, including consistency in rendering NULL
in conjunctions, "short-circuiting" of :func:`.and_` and :func:`.or_`
expressions which contain boolean constants, and rendering of
boolean constants and expressions as compared to "1" or "0" for backends
that don't feature ``true``/``false`` constants. [ticket:2804]