]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Ensure is_comparison passed for PG RANGE op() methods
authorJim Bosch <jbosch@astro.princeton.edu>
Sun, 26 Jul 2020 20:50:14 +0000 (16:50 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sun, 26 Jul 2020 20:57:13 +0000 (16:57 -0400)
commit07e57a0330fb7b1bbe0c59f442111a34e4b7c960
tree9310c47b7ceb59fce44b6f4b29d2d6571fcc7a4b
parent9e1ee412b8650761af6df993e119906682604728
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: 925b117e0c91cdd67d9ddbd9d65f5ca3e88af91f

Change-Id: I52ab4d4362d379c8253990f9d328a40990a64520
doc/build/changelog/unreleased_13/5476.rst [new file with mode: 0644]
lib/sqlalchemy/dialects/postgresql/ranges.py
test/dialect/postgresql/test_types.py