Closed guilhermeleobas closed 1 year ago
Before approving or requesting changes, I'll try it out and look into the typesystem issue.
Ok. I'll edit the first comment to include a description of what I did and what is currently supported. And about the typesystem issue, we don't have to address it right now, as the workaround I did works.
Closing it in favor of #537
Requires https://github.com/heavyai/heavydb-internal/pull/7126
This pull request adds support for three HeavyDB Geo column types (
GeoLineString
,GeoPoint
andPoint2D
) and common operations:is_null
set_null
get_item
/operator.__getitem__
set_item
/operator.__setitem__
get_n_of_values
__len__
Structure of each type:
Caveats
Parser doesn’t handle template specialization
Current parser implementation doesn’t handle subtype alias. So,
Column<GeoPoint>
isn’t redirected toHeavyDBColumnGeoPointType
, but ratherHeavyDBColumnType
. To circumvent this limitation, there’s a short-circuit inHeavyDBColumnType::postprocess_type
which redirects the implementation to the correct type.