Update jdbi3Version to v3.50.0 #3048
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.40.0->3.50.03.40.0->3.50.03.40.0->3.50.03.40.0->3.50.03.40.0->3.50.03.40.0->3.50.0Release Notes
jdbi/jdbi (org.jdbi:jdbi3-testcontainers)
v3.50.0JDK Baseline Update
3.50.0 is the first release of Jdbi to require Java 17. Thank you Java 11 for your service!
We intend to do occasional bug patches for significant bugs or security issues but there
will be no further active development work.
Experimental Java Native support
3.50.0 is the first release to support using Jdbi directly in native compilation. We only
support using the Java 25+ GraalVM toolchain and fully expect that there are bugs, breakages
and things that are not working well. If you use Jdbi in a native environment and find any
problems, we would be thrilled to get bug reports!
v3.49.6We have some problems with our upstream parent POM. There are changes
to Maven Central that require us to roll the parent POM into the Jdbi
project. This is a temporary thing and will go away as soon as
uploading parent poms to Central has been reenabled.
v3.49.5v3.49.4v3.49.3v3.49.2longupdate count from update statements (#2778)v3.49.1v3.49.0v3.48.0v3.47.0@JdbiRepositoryso aot generation works (#2727, thanks @hpoettker !)springmodule that will focus on Spring Framework 6.x and beyond. This is currently the same code as spring5 but no longer needs to maintain Spring Framework 5.x backwards compatibility.v3.46.0v3.45.4v3.45.3v3.45.2v3.45.1v3.45.0JdbiTestContainersExtension#setShutdownWaitTime(int)to control waiting for extension shutdown if a database is very slow. Addresses #2629 (thanks @stoyants).v3.44.1@Definitionfeature also supports super-interface definitionsv3.44.0@Definitionto define computed constantsConnection#commit()threw an Exception, we called commit() again. Now thecode explicitly calls
Connection#rollback(). Fixes #2595<T extends This<T>>(#2582, reported by @johnarrr)v3.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: #2592
Optionalor vavrOption(reported by @martyn0ff, #2558)fix SQL script parsing is (reported by @IrinaTerlizhenko, #2554).
integration-testmodule for tests that require different parts of the code base. Should be used to write test cases for issue investigations.nullas a value for binding bean, method, field and pojo objects (Suggested by @xak2000 in #2562)ResultSetfromCallstatements for databases that do not support cursor parameters. (suggested in #2557 by @metaforte and @0x1F528 in #2546)int,long,short,doubleandfloatreturn values from out parameters directly.v3.42.0@EnableJdbiRepositories, thanks @xfredk (#2528, #2544)v3.41.3-at the end of named parameters get swallowed. (#2499, thanks @gokristian for reporting).otjPostgressupport in jdbi-testing as the project shipped 1.02 with JPMS module name support.commons-compressdependabot issuev3.41.2otjPostgressupport in jdbi-testing. This will be undeprecated if they ship a version that provides an automatic module name for JPMS, otherwise it will be removed when Jdbi ships with full JPMS support.Handle#begin()beforeHandle#commit()(#2491, thanks @grigorem)v3.41.1.and-as part of named parameter names. (#2471)v3.41.0@Alpha(#2460)Configuration
📅 Schedule: Branch creation - "every 3 months on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.