refactor(common): move the geospatial module to the base SQL backend

it contains routines to compile geospatial values as SQL BREAKING CHANGE: removed `ibis.common.geospatial`, import the functions from `ibis.backends.base.sql.registry.geospatial`
ibis-project · Feb 8, 2023 · 3e7bfa3 · 3e7bfa3
1 parent 09a045c
commit 3e7bfa3
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/ibis/common/geospatial.py → .../backends/base/sql/registry/geospatial.py b/ibis/common/geospatial.py → .../backends/base/sql/registry/geospatial.py
diff --git a/ibis/backends/postgres/registry.py b/ibis/backends/postgres/registry.py
@@ -12,8 +12,8 @@
 import sqlalchemy as sa
 from sqlalchemy.dialects import postgresql as pg
 
+import ibis.backends.base.sql.registry.geospatial as geo
 import ibis.common.exceptions as com
-import ibis.common.geospatial as geo
 import ibis.expr.datatypes as dt
 import ibis.expr.operations as ops
 
@@ -383,7 +383,6 @@ def _literal(t, op):
         return sa.literal_column(f"INTERVAL '{value} {dtype.resolution}'")
     elif dtype.is_set():
         return list(map(sa.literal, value))
-    # geo spatial data type
     elif dtype.is_geospatial():
         # inline_metadata ex: 'SRID=4326;POINT( ... )'
         return sa.literal_column(geo.translate_literal(op, inline_metadata=True))