Skip to content

issue with DuckDB parsing #371

Description

@enjalot

I ran into an issue parsing numbers in JSON fields from a parquet file. I've reproduced with a simple test case here: https://observablehq.com/d/c5f796070b98c2a5

I submitted an issue with duckdb-wasm but the behavior works as expected in shell.duckdb.org so it may be the duckdb client in stdlib.
duckdb/duckdb-wasm#1267

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions