diff options
| author | Lele Gaifax <lele@metapensiero.it> | 2022-11-27 11:28:51 -0500 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2022-11-29 17:11:38 -0500 |
| commit | 0b239579f03c82f7669d77c238e4fda8638fb9c3 (patch) | |
| tree | ebe836c6d9f60362c4824843478122c7f725c2bd | |
| parent | 61443aa62bbef158274ae393db399fec7f054c2d (diff) | |
| download | sqlalchemy-0b239579f03c82f7669d77c238e4fda8638fb9c3.tar.gz | |
Add value-level hooks for SQL type detection; apply to Range
Added additional type-detection for the new PostgreSQL
:class:`_postgresql.Range` type, where previous cases that allowed the
psycopg2-native range objects to be received directly by the DBAPI without
SQLAlchemy intercepting them stopped working, as we now have our own value
object. The :class:`_postgresql.Range` object has been enhanced such that
SQLAlchemy Core detects it in otherwise ambiguous situations (such as
comparison to dates) and applies appropriate bind handlers. Pull request
courtesy Lele Gaifax.
Fixes: #8884
Closes: #8886
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8886
Pull-request-sha: 6e95e08a30597d3735ab38f2f1a2ccabd968852c
Change-Id: I3ca277c826dcf4b5644f44eb251345b439a84ee4
| -rw-r--r-- | doc/build/changelog/unreleased_20/8884.rst | 12 | ||||
| -rw-r--r-- | lib/sqlalchemy/dialects/postgresql/ranges.py | 20 | ||||
| -rw-r--r-- | lib/sqlalchemy/sql/sqltypes.py | 4 | ||||
| -rw-r--r-- | test/dialect/postgresql/test_compiler.py | 21 | ||||
| -rw-r--r-- | test/sql/test_types.py | 37 |
5 files changed, 94 insertions, 0 deletions
diff --git a/doc/build/changelog/unreleased_20/8884.rst b/doc/build/changelog/unreleased_20/8884.rst new file mode 100644 index 000000000..0edbb9553 --- /dev/null +++ b/doc/build/changelog/unreleased_20/8884.rst @@ -0,0 +1,12 @@ +.. change:: + :tags: bug, postgresql + :tickets: 8884 + + Added additional type-detection for the new PostgreSQL + :class:`_postgresql.Range` type, where previous cases that allowed the + psycopg2-native range objects to be received directly by the DBAPI without + SQLAlchemy intercepting them stopped working, as we now have our own value + object. The :class:`_postgresql.Range` object has been enhanced such that + SQLAlchemy Core detects it in otherwise ambiguous situations (such as + comparison to dates) and applies appropriate bind handlers. Pull request + courtesy Lele Gaifax. diff --git a/lib/sqlalchemy/dialects/postgresql/ranges.py b/lib/sqlalchemy/dialects/postgresql/ranges.py index a4c39d063..6f13d462a 100644 --- a/lib/sqlalchemy/dialects/postgresql/ranges.py +++ b/lib/sqlalchemy/dialects/postgresql/ranges.py @@ -11,6 +11,7 @@ import dataclasses from datetime import date from datetime import datetime from datetime import timedelta +from decimal import Decimal from typing import Any from typing import Generic from typing import Optional @@ -84,6 +85,10 @@ class Range(Generic[_T]): def __bool__(self) -> bool: return self.empty + @property + def __sa_type_engine__(self): + return AbstractRange() + def _contains_value(self, value: _T) -> bool: "Check whether this range contains the given `value`." @@ -622,6 +627,21 @@ class AbstractRange(sqltypes.TypeEngine): else: return super().adapt(impltype) + def _resolve_for_literal(self, value): + spec = value.lower if value.lower is not None else value.upper + + if isinstance(spec, int): + return INT8RANGE() + elif isinstance(spec, (Decimal, float)): + return NUMRANGE() + elif isinstance(spec, datetime): + return TSRANGE() if not spec.tzinfo else TSTZRANGE() + elif isinstance(spec, date): + return DATERANGE() + else: + # empty Range, SQL datatype can't be determined here + return sqltypes.NULLTYPE + class comparator_factory(sqltypes.Concatenable.Comparator): """Define comparison operations for range types.""" diff --git a/lib/sqlalchemy/sql/sqltypes.py b/lib/sqlalchemy/sql/sqltypes.py index 624b7d16e..308c233e4 100644 --- a/lib/sqlalchemy/sql/sqltypes.py +++ b/lib/sqlalchemy/sql/sqltypes.py @@ -3682,6 +3682,10 @@ _type_map_get = _type_map.get def _resolve_value_to_type(value: Any) -> TypeEngine[Any]: _result_type = _type_map_get(type(value), False) + + if _result_type is False: + _result_type = getattr(value, "__sa_type_engine__", False) + if _result_type is False: # use inspect() to detect SQLAlchemy built-in # objects. diff --git a/test/dialect/postgresql/test_compiler.py b/test/dialect/postgresql/test_compiler.py index 431cd7ded..ee3372c74 100644 --- a/test/dialect/postgresql/test_compiler.py +++ b/test/dialect/postgresql/test_compiler.py @@ -42,6 +42,7 @@ from sqlalchemy.dialects.postgresql import ExcludeConstraint from sqlalchemy.dialects.postgresql import insert from sqlalchemy.dialects.postgresql import JSONB from sqlalchemy.dialects.postgresql import JSONPATH +from sqlalchemy.dialects.postgresql import Range from sqlalchemy.dialects.postgresql import TSRANGE from sqlalchemy.dialects.postgresql.base import PGDialect from sqlalchemy.dialects.postgresql.psycopg2 import PGDialect_psycopg2 @@ -2397,6 +2398,26 @@ class CompileTest(fixtures.TestBase, AssertsCompiledSQL): "AS jsonb_path_exists_1 FROM data", ) + def test_custom_object_hook(self): + # See issue #8884 + from datetime import date + + usages = table( + "usages", + column("id", Integer), + column("date", Date), + column("amount", Integer), + ) + period = Range(date(2022, 1, 1), (2023, 1, 1)) + stmt = select(func.sum(usages.c.amount)).where( + usages.c.date.op("<@")(period) + ) + self.assert_compile( + stmt, + "SELECT sum(usages.amount) AS sum_1 FROM usages " + "WHERE usages.date <@ %(date_1)s::DATERANGE", + ) + class InsertOnConflictTest(fixtures.TablesTest, AssertsCompiledSQL): __dialect__ = postgresql.dialect() diff --git a/test/sql/test_types.py b/test/sql/test_types.py index d1b32186e..91413ff35 100644 --- a/test/sql/test_types.py +++ b/test/sql/test_types.py @@ -3293,6 +3293,43 @@ class ExpressionTest( ], ) + @testing.variation("secondary_adapt", [True, False]) + @testing.variation("expression_type", ["literal", "right_side"]) + def test_value_level_bind_hooks( + self, connection, metadata, secondary_adapt, expression_type + ): + """test new feature added in #8884, allowing custom value objects + to indicate the SQL type they should resolve towards. + + """ + + class MyFoobarType(types.UserDefinedType): + if secondary_adapt: + + def _resolve_for_literal(self, value): + return String(value.length) + + class Widget: + def __init__(self, length): + self.length = length + + @property + def __sa_type_engine__(self): + return MyFoobarType() + + if expression_type.literal: + expr = literal(Widget(52)) + elif expression_type.right_side: + expr = (column("x", Integer) == Widget(52)).right + else: + assert False + + if secondary_adapt: + is_(expr.type._type_affinity, String) + eq_(expr.type.length, 52) + else: + is_(expr.type._type_affinity, MyFoobarType) + def test_grouped_bind_adapt(self): test_table = self.tables.test |
