Add support for DuckDB Geospatial extensions
Closed this issue · 3 comments
What
Now that DuckDB serves as pg_lakehouse
query engine, it'd be very useful if it was possible to leverage both official and unofficial extensions in queries targeting foreign tables.
In our specific case we would be interested in https://github.com/isaacbrodsky/h3-duckdb & https://github.com/duckdb/duckdb_spatial/
Why
Unlock different use cases.
What Now that DuckDB serves as
pg_lakehouse
query engine, it'd be very useful if it was possible to leverage both official and unofficial extensions in queries targeting foreign tables.In our specific case we would be interested in https://github.com/isaacbrodsky/h3-duckdb & https://github.com/duckdb/duckdb_spatial/
Why Unlock different use cases.
We'll likely proceed on a case-by-case basis for the extensions to support from DuckDB. Both of the ones you link here seems related to Geospatial, which we should definitely support.
I'll re-scope the issue.
I am glad to try this ticket.
I am glad to try this ticket.
Thank you!