Closed bbigras closed 6 years ago
I think the issue is very likely, that we do not infer the type based on the rust type, but let it be figured out by the odbc driver itself. We should consider passing something different to Unknown
in this piece of code:
I've created a branch with possible fix, but I can't test it right now as I have no access to SQL Server and it works in either way in Postgres
I'll test it at work tomorrow.
Sorry for the duplicate post. I replied with the wrong account.
I don't have the "Invalid data type" problem anymore.
I tested with a simple query and it was fine. I tested with a query with 3 "INNER JOIN" and the requests hangs for about 20 seconds and the query results contain 0 when it shouldn't be. Not sure if I should open another issue or if it could be related.
Also I think you might be able to use the microsoft/mssql-server-linux docker image[1] for your unit tests.
@bbigras I've released invalid data type fix as 0.9.0. Could you please check if other problem (with joins) is resolved now? If not, we could move this to a separate bug and it would be great to share some additional details and examples like SQL query, table structure etc
I filled a new issue: #53
error
code
rustc 1.19.0-nightly (cfb5debbc 2017-06-12) odbc b88e6837704aafbcfd23a7bdc8556a7b6f02a20e Driver=FreeTDS freetds 1.00.40-1 Arch Linux 64-bit