Michael König

Glad to hear that there is a workaround by using another driver. I will have to investigate to find out what the invalid precision value would be.

Sorry, no news on this one so far. I had too little time in the past to investigate.

Sorry, not yet :-(

Hi! Thanks for reporting! Time columns are indeed not supported yet. By the way, if you are looking for sheer performance for PostgreSQL, try [psycopg2](https://github.com/psycopg/psycopg2) or [asyncpg](https://github.com/MagicStack/asyncpg); the official PostgreSQL...

Hello @IceS2! Thanks for reporting! You did well :-). I have a hunch that the `prefer_unicode=True` in combination with `fetchallarrow()` is the culprit here, as I fear that this code...

@IceS2 Hi again! Have you tried using more recent versions of turbodbc/pyarrow in the mean time? Does this fix things?

@xhochy Would you have the time to look at @albertoRamon 's reproducing example, please?

Would it work to switch to the conda environment with our "blessed" builds?

@albertoRamon Could you try using the turbodbc conda package, please? https://anaconda.org/conda-forge/turbodbc

Anything too modern will not work because the precompiled pyarrow wheel uses a "classic" version of the ABIs, while pip install turbodbc will compile stuff with the latest and greatest...