Mark
How is your data ingested into DuckDB? Are you inserting through Pandas DataFrames, CSV files, or inserting through prepared statements?
It is likely the unicode ingestion verification there is missing or incomplete - we can have a look to see if we can create a reproducible example by intentionally creating...
Thanks for the report! This should be fixed by #4414, after that gets ported to the JDBC client.
I don't think we want to add `duckdb_value_decimal_as_properties` and I think having `duckdb_value_decimal` return 0 if the value is not a decimal seems acceptable to me. The reason `duckdb_value_decimal` exists...
#4414 should solve this, but it is still a work in progress. In the meantime you can use multiple cursors spawned from the same connection instead of opening multiple connections...
> > #4414 should solve this, but it is still a work in progress. In the meantime you can use multiple cursors spawned from the same connection instead of opening...
This should be fully resolved now that jemalloc is merged (#4971) and we stream data to disk optimistically (#4996). Feel free to re-open if you are still hitting the issue.
Perhaps you could discuss this with @Maxxen?
Closing this until @pdet has time to pick it up again