Jim Bosch a8c9e8d723 Ensure is_comparison passed for PG RANGE op() methods ...

Fixed issue where the return type for the various RANGE comparison
operators would itself be the same RANGE type rather than BOOLEAN, which
would cause an undesirable result in the case that a
:class:`.TypeDecorator` that defined result-processing behavior were in
use.  Pull request courtesy Jim Bosch.

Fixes: #5476
Closes: #5477
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5477
Pull-request-sha: 925b117e0c

Change-Id: I52ab4d4362d379c8253990f9d328a40990a64520
(cherry picked from commit 07e57a0330)

2020-07-26 16:57:43 -04:00

..

__init__.py

refactor test suites for postgresql, mssql, mysql into packages.

2013-06-28 22:30:11 -04:00

test_compiler.py

Add with_for_update mysql new functionalities

2020-05-24 05:32:32 -06:00

test_dialect.py

Revise psycopg2 execute_values approach

2019-08-18 13:25:25 -04:00

test_on_conflict.py

Post black reformatting

2019-01-06 18:23:11 -05:00

test_query.py

Pass connection to TablesTest.insert_data()

2020-04-15 11:16:12 -04:00

test_reflection.py

Don't include PG INCLUDE columns as regular index columns

2020-03-18 19:29:05 -04:00

test_types.py

Ensure is_comparison passed for PG RANGE op() methods

2020-07-26 16:57:43 -04:00