Replies: 1 comment
-
The described behavior of If you want an alternate converter that is similar to the built-in JSON converter but handles these values differently, it's easy enough to create your own. Just take a look at the code for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working with a parquet file which has a
INT64
field.When using the COPY command in duckdb sql
COPY ( ... ) TO 'sample.json';
it serializes the field as a json number.
When using
JsonDuckDBValueConverter
on the same data, it serializes as a json string.I understand why
JsonDuckDBValueConverter
uses a string on anINT64
, but I expect the behaviour to be the same as the COPY command.The particular field value is within the range for json numbers (
1489090316
)Beta Was this translation helpful? Give feedback.
All reactions