hb2638

We have the same problem. We created a gitlab runner ( https://docs.gitlab.com/runner/configuration/runner_autoscale_aws_fargate/ ) that has VS Build Tools 2019. It will start up but will blow up as we start...

> I would very much like them to be consistent. > > I'm just not sure what the right answer is. Is the DB always in UTC and we should...

I'm using this as a workaround for the moment which converts datetime objects with a timezone to a string ``` def fixup_args(cursor: pyodbc.Cursor, args: typing.List) -> typing.List: return [a.isoformat() if...

Thanks for reporting this. I started upgrading our code base from pydantic 1.X to 2.X yesterday and hit this bug. This is the hack/workaround I'm using for now... set it...

I just hit this bug. Thx for reporting!!!

This bug is still present in 1.10.5. Thx for reporting!!

Why was this bug closed? The bug is still present in the code. "When we validate a set, we always re-create it" contradicts **copy_on_model_validation** being set to 'none'. The code/validator...

> https://learn.microsoft.com/en-us/sql/odbc/reference/syntax/sqlexecdirect-function?view=sql-server-ver16 > > "When SQLExecDirect returns either SQL_ERROR or SQL_SUCCESS_WITH_INFO, an associated SQLSTATE value can be obtained by calling SQLGetDiagRec with a HandleType of SQL_HANDLE_STMT and a Handle of...

> Compare your ODBC traces. There is no message returned in the NOCOUNT ON case. > SET NOCOUNT ON returns (SQL_NO_DATA_FOUND) SET NOCOUNT OFF returns (SQL_SUCCESS_WITH_INFO) It's right there on...

This is a pyodbc issue, not a driver issue. Microsoft’s documentation says you need to call SQLGetDiagRec or SQLGetDiagField on almost all response codes, including the no data one. may...