Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support the DuckDB MAP type #600

Open
JelteF opened this issue Feb 14, 2025 · 0 comments
Open

Support the DuckDB MAP type #600

JelteF opened this issue Feb 14, 2025 · 0 comments
Labels
types Issues related to type conversions

Comments

@JelteF
Copy link
Collaborator

JelteF commented Feb 14, 2025

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:

  1. If people actually select a MAP column in the output of their query, we should probably just convert it to its text representation.
  2. 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.

Once we do this we can un-exclude:

@JelteF JelteF added the types Issues related to type conversions label Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
types Issues related to type conversions
Projects
None yet
Development

No branches or pull requests

1 participant