Try a simpler approach for handling Timestamps on SQL Server

[labkey-adam]

Rationale

More research in the SQL Server JDBC issues list suggests a possible approach for sending Timestamps via JDBC using a standard string format that doesn't vary based on language settings. Turns out the 12.6.3 version of the JDBC driver introduced an issue where the driver failed to parse timestamps returned from the database when parameters were sent setting the explicit Types.TIMESTAMP type. (Ironically, the bug was introduced as part of the fix to a Timestamp + stored procedure issue that I filed earlier with the team.) That forced us to always omit the type when setting Timestamp parameters in our statement wrapper, which lead to the need to vary the timestamp format we sent based on locale. The latest (12.8.1) version fixes this issue, so I'm hopeful we can return to setting the explicit type which seems to then universally support the ISO-style format.

• 12.6.3+ changed behavior on how it handles timezones for jdbcType TIMESTAMP microsoft/mssql-jdbc#2490
• Conversion exception when calling a stored procedure with a datetime in-out parameter while setting a String value microsoft/mssql-jdbc#2436

Related Pull Requests

• Fix SQL Server timestamp handling with non-US date formats #5805