dependabot[bot] opened a new pull request, #3306: URL: https://github.com/apache/arrow-adbc/pull/3306
Bumps [com.microsoft.sqlserver:mssql-jdbc](https://github.com/Microsoft/mssql-jdbc) from 13.1.1.jre11-preview to 13.2.0.jre11. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Microsoft/mssql-jdbc/releases";>com.microsoft.sqlserver:mssql-jdbc's releases</a>.</em></p> <blockquote> <h2>[13.2.0] Stable Release</h2> <h3>Changed</h3> <ul> <li><strong>Use sys.all_objects for accurate function and procedure filtering</strong> <a href="https://redirect.github.com/microsoft/mssql-jdbc/pull/2705";>#2705</a> <strong>What changed</strong>: Differentiated stored procedures and functions using sys.all_objects instead of sp_stored_procedures. <strong>Who benefits</strong>: Developers using getProcedures() and getFunctions() in JDBC. <strong>Impact</strong>: Ensures correct metadata retrieval, preventing confusion from mixed results.</li> </ul> <h3>Fixed issues</h3> <ul> <li> <p><strong>Fix trustStoreType JVM property consultation in SSL Connections</strong> <a href="https://redirect.github.com/microsoft/mssql-jdbc/pull/2724";>#2724</a> <strong>What was fixed</strong>: Ensured fallback to JVM system property javax.net.ssl.trustStoreType if connection property is unset. <strong>Who benefits</strong>: Users configuring SSL via system properties. <strong>Impact</strong>: Enables proper SSL trust store resolution, improving compatibility with system configurations.</p> </li> <li> <p><strong>Addressed a data integrity and performance issue for bulk copy batch inserts with non-Unicode Strings</strong> <a href="https://redirect.github.com/microsoft/mssql-jdbc/pull/2735";>#2735</a> <strong>What was fixed</strong>: Resolved performance degradation and incorrect string handling in bulk copy batch inserts when useBulkCopyForBatchInsert=true and sendStringParametersAsUnicode=false. <strong>Who benefits</strong>: Applications using SQL Server JDBC Bulk Copy for high-volume inserts, especially with non-Unicode or accented character data. <strong>Impact</strong>: Restores expected string storage, improves bulk insert performance for bulk copy API.</p> </li> <li> <p><strong>Handle SQL comments at start of query in getGenerateKeys() method</strong> <a href="https://redirect.github.com/microsoft/mssql-jdbc/pull/2731";>#2731</a> <strong>What was fixed</strong>: Corrected detection of INSERT statements when preceded by SQL comments. <strong>Who benefits</strong>: Developers using getGeneratedKeys() after commented SQL inserts. <strong>Impact</strong>: Fixes previously failing key retrieval when comments are present before the query.</p> </li> <li> <p><strong>Fix update count handling for multi-statement queries executed via PreparedStatement execute method.</strong> <a href="https://redirect.github.com/microsoft/mssql-jdbc/pull/2737";>#2737</a> <strong>What was fixed</strong>: Corrected update count handling for multi-statement queries run using PreparedStatement execute method, ensuring accurate counts for INSERT and other DML operations. <strong>Who benefits</strong>: Java applications using SQL Server JDBC with multi-statement PreparedStatement executions. <strong>Impact</strong>: Eliminates inconsistent update counts between Statement and PreparedStatement, improving reliability of result processing logic.</p> </li> <li> <p><strong>CodeQL suppression fixes</strong> <a href="https://redirect.github.com/microsoft/mssql-jdbc/pull/2728";>#2728</a> <strong>What was fixed</strong>: Suppressed CodeQL rule [SM05141] with justification for broader usage scenarios. <strong>Who benefits</strong>: Developers maintaining code quality tools like CodeQL. <strong>Impact</strong>: Prevents unnecessary alerts for valid usage in multi-environment libraries.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Microsoft/mssql-jdbc/commits";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
