Bump org.jdbi:jdbi3-core from 3.42.0 to 3.44.0

[dependabot]

Bumps org.jdbi:jdbi3-core from 3.42.0 to 3.44.0.

Release notes

Sourced from org.jdbi:jdbi3-core's releases.

v3.44.0

3.44.0

• New Feature: annotate types, methods, or fields as @Definition to define computed constants
• fix edge condition when calling Connection#commit() threw an Exception, we called commit() again. Now the code explicitly calls Connection#rollback(). Fixes #2595
• FieldMapper: skip static fields (#2607, reported by @​mvysny)
• fix StackOverflowError when encountering recursive types like <T extends This<T>> (#2582, reported by @​johnarrr)

JDBI 3.43.0

• Support nesting row types into Java Optional or vavr Option (reported by @​martyn0ff, #2558)
• finally give up on trying to guess SQL script parsing and add a switch to control whether to strip trailing semicolons or not. Another attempt to fix SQL script parsing is (reported by @​IrinaTerlizhenko, #2554).
• add a new integration-test module for tests that require different parts of the code base. Should be used to write test cases for issue investigations.
• support null as a value for binding bean, method, field and pojo objects (Suggested by @​xak2000 in #2562)
• Add testcontainers support for MS SQLServer
• support returning a ResultSet from Call statements for databases that do not support cursor parameters. (suggested in #2557 by @​metaforte and @​0x1F528 in #2546)
• support int, long, short, double and float return values from out parameters directly.

Changelog

Sourced from org.jdbi:jdbi3-core's changelog.

3.44.0

• New Feature: annotate types, methods, or fields as @Definition to define computed constants
• fix edge condition when calling Connection#commit() threw an Exception, we called commit() again. Now the code explicitly calls Connection#rollback(). Fixes #2595
• FieldMapper: skip static fields (#2607, reported by @​mvysny)
• fix StackOverflowError when encountering recursive types like <T extends This<T>> (#2582, reported by @​johnarrr)

3.43.0

** POTENTIAL BREAKING CHANGE **

With 3.43.0, we have improved the support for calling stored procedures via Call, and in particular returning result sets. Like any object that comes from a Statement, the expectation is that code will consume all results (whether it's "normal" result set or a stored procedure result) before closing the Statement. However, previously, Jdbi did not enforce this - OutParameters could be used after the statement closed.

So, you might observe new exceptions while trying to use OutParameters after closing the Call they came from. See: jdbi/jdbi#2592

• Support nesting row types into Java Optional or vavr Option (reported by @​martyn0ff, #2558)
• finally give up on trying to guess SQL script parsing and add a switch to control whether to strip trailing semicolons or not. Another attempt to fix SQL script parsing is (reported by @​IrinaTerlizhenko, #2554).
• add a new integration-test module for tests that require different parts of the code base. Should be used to write test cases for issue investigations.
• support null as a value for binding bean, method, field and pojo objects (Suggested by @​xak2000 in #2562)
• Add testcontainers support for MS SQLServer
• support returning a ResultSet from Call statements for databases that do not support cursor parameters. (suggested in #2557 by @​metaforte and @​0x1F528 in #2546)
• support int, long, short, double and float return values from out parameters directly.

Commits

• 56ed914 [maven-release-plugin] prepare release v3.44.0
• 117e108 release notes 3.44.0
• 78dbaf1 SqlObject: add @Definition annotation for defining computed constants
• 648740c doc: update Spring section to call out Spring 6 to not scare off users
• f7136bb Merge pull request #2615 from hgschmie/basepom-58
• 67d03fb Update to basepom 58
• 3d7f23e Merge pull request #2612 from hgschmie/versions-fix
• 7d5e6af Merge pull request #2614 from hgschmie/setup-java
• a112881 update setup-java action version
• 174a17b Fix clickhouse jdbc driver version
• Additional commits viewable in compare view

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 commands and options

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)

[dependabot]

Superseded by #35.