]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2581ae6) | patch
Use base __ne__ implementation for range types w/ None
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 3 Apr 2018 19:35:00 +0000 (15:35 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 3 Apr 2018 19:37:36 +0000 (15:37 -0400)
commita2499837456dc09109366c4b5f94aca1343e44f8
treea2d619e4326efa3a3da4ae7ed2504827cd2df8f6tree | snapshot
parent2581ae686c1ce91397e2a8a824febf344698df1ecommit | diff
Use base __ne__ implementation for range types w/ None

Fixed bug where the special "not equals" operator for the Postgresql
"range" datatypes such as DATERANGE would fail to render "IS NOT NULL" when
compared to the Python ``None`` value.

Also break up range tests into backend round trip and straight
compilation suites.

Change-Id: Ibaee132b1ea7dac8b799495a27f98f82a7d9c028
Fixes: #4229
(cherry picked from commit e1ac5dc63cc13cfbabe0ec7fbb3521bfb1b7b750)
doc/build/changelog/unreleased_12/4229.rst [new file with mode: 0644] blob
lib/sqlalchemy/dialects/postgresql/ranges.py diff | blob | blame | history
test/dialect/postgresql/test_types.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git