Markus Klein
Markus Klein
Hello @timrburnham , thanks for the detailed response and sorry for the delayed answer. The use case is legit, however it is quite removed from there `arrow-odbc` is currently in...
I fear it is a problem with the ODBC standard 😅 ODBC 4.0 is going to fix this since it allows to define exception behavior for truncation then fetching data....
Hi @leo-schick , you can make it work, by setting the `--column-length-limit 8000` option. Should have mentioned this option in the past before 😅 . I also did not find...
@leo-schick Does the flag work for you?
ODBC 4.0 is going to specify length exception behaviour (. I do not know when it will release, and when support will be wide spread. Until then it seems to...
@BratSinot Fetching data asynchronously works with ODBC if: 1. You know the schema in advance (currently you can not query the metadata (i.e. the schema information) of the result set...
Hope the current documentation is sufficient. Closing this issue for now.
Also closing this issue, as the converted type **is** written into the output by `odbc2parquet`. Fault seems to lie with readers. Please open a bug there, if you need these...
A little update. This works today using `tokio::task::spawn_local` instead of `tokio::spawn`. No mutex around the connection required. I am also currently evaluating the safety of making statements `Send`, which should...
See also upstream issue about supporting other Time units than Nanoseconds for Time: