You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Postgres does not support a generic MAP type. So we need to make some concessions here. But what we can do is the following:
If people actually select a MAP column in the output of their query, we should probably just convert it to its text representation.
To allow operations on it like indexing, should define a new Postgres type called duckdb.map and implement the index/subscript operator on it. That subscript operator should then return a duckdb.unresolved_type, similarly to how the index/subscript operator is implemented on duckdb.unresolved_type.
Description
Postgres does not support a generic MAP type. So we need to make some concessions here. But what we can do is the following:
duckdb.map
and implement the index/subscript operator on it. That subscript operator should then return aduckdb.unresolved_type
, similarly to how the index/subscript operator is implemented onduckdb.unresolved_type
.Once we do this we can un-exclude:
pg_duckdb/test/regression/expected/test_all_types.out
Line 18 in 02ebeae
The text was updated successfully, but these errors were encountered: