weird schema when reading parquet with decimal dtypes

[universalmind303]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce

From duckdb cli

D CALL dbgen(sf = 1);
D copy (select * from customer) to './tpch/customer.parquet';
D copy (select * from lineitem) to './tpch/lineitem.parquet';
D copy (select * from nation) to './tpch/nation.parquet';
D copy (select * from orders) to './tpch/orders.parquet';
D copy (select * from part) to './tpch/part.parquet';
D copy (select * from partsupp) to './tpch/partsupp.parquet';
D copy (select * from region) to './tpch/region.parquet';
D copy (select * from supplier) to './tpch/supplier.parquet';

then from daft

import daft
daft.read_parquet(f"./tpch/lineitem.parquet").schema()

╭─────────────────┬───────╮
│ Column Name     ┆ Type  │
╞═════════════════╪═══════╡
│ l_orderkey      ┆ Int64 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_partkey       ┆ Int64 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_suppkey       ┆ Int64 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_linenumber    ┆ Int64 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_quantity      ┆ 15.2  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_extendedprice ┆ 15.2  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_discount      ┆ 15.2  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_tax           ┆ 15.2  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_returnflag    ┆ Utf8  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_linestatus    ┆ Utf8  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_shipdate      ┆ Date  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_commitdate    ┆ Date  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_receiptdate   ┆ Date  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_shipinstruct  ┆ Utf8  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_shipmode      ┆ Utf8  │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌┤
│ l_comment       ┆ Utf8  │
╰─────────────────┴───────╯

Expected behavior
dtype should be Decimal(precision=15, scale=2), not 15.2

Additional context
duckdb version: v1.1.0

[samster25]

I think it maybe something wrong with the repr? I wondering if it was hit during @raunakab display trait changes

[raunakab]

I think it maybe something wrong with the repr? I wondering if it was hit during @raunakab display trait changes

This is probably it. I'll take a look into this asap.

[raunakab]

Updated and pushed a fix. Waiting for reviews to merge it in now.