Dave Hirschfeld

***xref:*** https://github.com/python-trio/trio-asyncio/issues/22#issuecomment-586974857

@jrmlhermitte - that level of git experience is so far above most analysts that you'd be excluding a lot of people and introducing a huge barrier to contribution. As @mrocklin...

As @xhochy mentioned, `turbodbc` *is* available from the **`conda-forge`** channel: ``` (base) C:\> conda search 'turbodbc>=3.1' Loading channels: done # Name Version Build Channel turbodbc 3.1.0 py36h51f579c_0 conda-forge turbodbc 3.1.0...

Try enabling [`faulthandler`](https://docs.python.org/3/library/faulthandler.html#faulthandler.enable) to get more context.

Not particularly enlightening, unfortunately.

***xref:*** #142

Thanks @MathMagique - I'll try out other drivers and report back my success... or otherwise :|

Unfortunately no joy with any of: ``` 'Oracle in OraClient11g_x64_home1' 'Oracle in XE' 'Oracle in instantclient_11_2' ``` Querying the same database/table with cx_oracle does work so maybe they have some...

The offending column is of type `NUMBER(6)`. [It seems](https://docs.oracle.com/cd/E85694_01/ODPNT/entityDataTypeMapping.htm#ODPNT8467) `NUMBER(6)` should map to an `int32` rather than an `int64`

...since pyodbc can query the data with the same driver/SQL it would seem the issue lies in turbodbc - even if the issue is that Oracle drivers don't support the...