]> 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:43 +0000 (16:57 -0400)
commita8c9e8d723056357bf1f2776d3677d55e8a28aa6
tree3dc0177a5a3d60b686102ca65dd567b49fe81208
parente967c13e0878f4d5f8fbdb6584261d0a92e7c1a3
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
(cherry picked from commit 07e57a0330fb7b1bbe0c59f442111a34e4b7c960)
doc/build/changelog/unreleased_13/5476.rst [new file with mode: 0644]
lib/sqlalchemy/dialects/postgresql/ranges.py
test/dialect/postgresql/test_types.py