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
Thanks for your interest! I defer to @Tishj there on whether that makes sense and what the implementation plan should be. Most likely this should build on top of #56 / #97 where enums are copied from Postgres to the DuckDB catalog.
@wuputah Thanks for your suggestion. I'll try to implement some types which are compatible now. I have some questions want to ask.
Are there any discuss about how to implement some types which are incompatible? And what is the principle.
Could you elaborate on the relationship between the catalog system implemented in this patch and the support for enum types? How does the catalog system specifically enable or facilitate the implementation of enum type support? Can you provide a concrete example of how the catalog changes in this patch would be utilized when implementing enum type support in pg_duckdb? Thanks!
No description provided.
The text was updated successfully, but these errors were encountered: