]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
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:36:48 +0000 (15:36 -0400)
commite1ac5dc63cc13cfbabe0ec7fbb3521bfb1b7b750
tree8c8e587ae18a43a680bdde1799a6d8c4fb92144a
parent9f986ce10c6755af3f347a56f9ea03e0e2c5943e
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
doc/build/changelog/unreleased_12/4229.rst [new file with mode: 0644]
lib/sqlalchemy/dialects/postgresql/ranges.py
test/dialect/postgresql/test_types.py