Types with all the same type return as string and not as struct
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the PostgreSQL composite-type examples through the Python client, using the provided CREATE TYPE statements and a simple SELECT. Done means composite types whose fields share one type are returned as structured values rather than strings, with regression coverage for both the text and boolean examples.
Written by the indexing model from the issue text.
Description
What happens?
If I do a really complex type in postgres, everything works. However if I have a types like this:
CREATE TYPE common.name_type AS (
de text, fr text, it text
)
CREATE TYPE common.cluster_boolean AS (
g BOOLEAN, p BOOLEAN, s BOOLEAN, b BOOLEAN, h BOOLEAN
);
DuckDB will return it as string in the form: (value1,value2,value3), which is almost unusable (especially for the boolean case)
To Reproduce
- Create a type as above in postgres
- insert some data
- do a simple select on it
OS:
Windows
PostgreSQL Version:
17.5
DuckDB Version:
1.3.2
DuckDB Client:
Python
Full Name:
Adrian Ehrsam
Affiliation:
Building Material Suisse
Have you tried this on the latest main branch?
- I agree
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
- I agree
- Dominant language
- C++
- Stars
- 372
- Forks
- 107
- Avg merge
- 13h 55m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from duckdb/duckdb-postgres
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#575 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
duckdb/duckdb-postgres#564 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
duckdb/duckdb-postgres#491 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#487 · 1 comment ·
Maintainers usually reply within 1 day
-
After `COPY DATABASE FROM <pg>`, the types from pg are improperly formatted in `EXPORT` commandsOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#429 ·
Maintainers usually reply within 1 day
All issues in duckdb/duckdb-postgres
Similar issues
-
Component: Python API
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Vector35/binaryninja-api#8649 ·
Maintainers usually reply within 3 days
-
ai_p2 comp-parquet-reader-v3
Difficulty 2/5 Half a day Newbie friendliness 66/100
ClickHouse/ClickHouse#124986 ·
Maintainers usually reply within 1 day
-
bug product: very_good_flutter_plugin
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
VeryGoodOpenSource/very_good_templates#654 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AcademySoftwareFoundation/OpenImageIO#5550 ·
Maintainers usually reply within 2 days