Michael Kleehammer

I think my suggestion above might be the way to go: https://learn.microsoft.com/en-us/sql/odbc/reference/develop-app/multiple-results?view=sql-server-ver16 > If one of the statements in a batch fails, SQLMoreResults will return either SQL_ERROR or SQL_SUCCESS_WITH_INFO. If...

I just built the py3 branch with a debug version of Python 3.12 and the PostgreSQL tests pass. I did comment out the fast executemany code temporarily until I can...

I've merged 5.0 into the master branch and released 5.0.0 alpha 2. Please see the discussion [here](https://github.com/mkleehammer/pyodbc/discussions/1254)

The threadsafety is a read-only flag required by the DBAPI to indicate pyodbc can be used on multiple threads. The *driver* needs to also be threadsafe too, but pyodbc itself...

Earlier releases did not include Apple Silicon / ARM binary wheels, but we've added them to 5.0.0 beta 2. If you can, please test them. Details here: https://github.com/mkleehammer/pyodbc/discussions/1263

I'm going to close this for inactivity. If someone could confirm with 2.3.9 it would be useful.

The right way would probably be to rewrite the array parameter code to scan the parameters before performing the actual bind. It could make a best guess on the first...

Well, the py3 branch builds on Python 3.12 on Ubuntu, without fast_execute_many, and works with the PostgreSQL unit tests. My conversion task list of this topic has a bunch of...

I've merged 5.0 with Python 3.12 support into the master branch and published 5.0.0 alpha2. I'll make a final release of 5.0.0 in the next few days if no serious...

> Also, 4.0.34 version of pyODBC has a major problem with including its own old unixODBC which contains much bugs, use '32 for the time being. I don't remember this....