FreeTDS | A FreeTDS project compiling for iOS and macOS via xcode | iOS library

There is a protocol to allow a single connection to have multiple concurrent queries running at the same time. It's called Multiple Active Result Sets, and I have no idea if FreeTDS uses it, but the Microsoft ODBC Driver can.

However the execution of mutliple queries on a single connection is interleaved not concurrent. If you want two queries to actually execute at the same time, use two connections.

The problem was that the Databricks SQL driver does not yet support ARM, which my laptop and Docker container was building for. See ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib '/opt/simba/spark/lib/64/libsparkodbc_sb64.so' : file not found (0) (SQLDriverConnect)")

I updated my repo at https://github.com/rlorenzo/databricks_php with a working example and forced the container to build an x86 version.

Will update my repo if Databricks ever supports ARM.

Hope this helps someone in the future.

Compiler is simply complaining about a build time dependency, cc1 tool should be in your system to build pyodbc.

In Ubuntu you can solve this with

No, because odbc_connect= is part of the pyodbc driver code in SQLAlchemy and the pymssql driver code has no corresponding option. That said, pymssql was actively supported in SQLAlchemy until recently, so if you need to pass any extra options to pymssql there is probably a way to do it. Check the documentation for details.

I have answered question 1 myself. If anyone else can give me a definitive answer to part two, I will happily mark that as the answer.

I guessed that I needed to download and install the mingw packages that couldn't be downloaded somewhere. I did a bit of trawling and found this article (Offline installation of packages)which gave me the pointers I needed. I got these four files from https://repo.msys2.org/mingw/mingw64/:

I brew reinstalled readline and this fixed the issue.

Coming from Sybase, and having written the book on ASE... it is true that ASE T-SQL and MSSQL T-SQL still have many similarities, so from that perspective things may work. However, there are also many nasty little differences. To name just a random few aspects: the empty string (a single space in ASE, really empty in MSSQL), string concatenation with NULL (MSSQL has moved away from what is still the Sybase default), the T-SQL OJ syntax (no longer supported in MSSQL and neither in Babelfish); different behaviour by some BIFs in some cases (SUBSTRING(), SPACE()), BIFs that SQL Server does not have, different syntax for RAISERROR and PRINT, CREATE TYPE/sp_addtype differences, @@FETCH_STATUS, different syntax for hints, ROLLBACK TRIGGER, extended GROUP-BY syntax. And then there's things like CREATE DATABASE/ALTER DATABASE options, QUIESCE DATABASE, replication, partitioning, that's different. As for connectivity: FreeTDS may work, but from a Babelfish perspective this is not actually supported. In summary: you mileage may vary. Both syntactically and semantically there will be differences that may impact your migration, so while some parts may work, you may need to patch up your ASE SQL code before Babelfish would accept it.

SOLVED

Dockerfile:

Thanks to @FlipperPA. In short, the solution I take is to set the "text size" parameter of /etc/freetds/freetds.conf or /var/lib/postgresql/.freetds.conf to the maximum value (4294967295):