-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency org.jdbi:jdbi3-sqlobject to v3.48.0 #98
Open
renovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/org.jdbi-jdbi3-sqlobject-3.x
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0204c13
to
70e6792
Compare
70e6792
to
2e6fcf4
Compare
2e6fcf4
to
b1da230
Compare
b1da230
to
1dd32e8
Compare
1dd32e8
to
2a379dc
Compare
2a379dc
to
ac4cf36
Compare
ac4cf36
to
84a9a2b
Compare
84a9a2b
to
a16e903
Compare
a16e903
to
e95dbe7
Compare
e95dbe7
to
f0d9aaa
Compare
f0d9aaa
to
fe66d1a
Compare
fe66d1a
to
f22a5ff
Compare
f22a5ff
to
42ba7b0
Compare
42ba7b0
to
691b0e6
Compare
691b0e6
to
7cd5336
Compare
7cd5336
to
8c3d977
Compare
5cf3319
to
0cd98e5
Compare
0cd98e5
to
60f38a3
Compare
60f38a3
to
159fd30
Compare
159fd30
to
9ef3b04
Compare
9ef3b04
to
6807b05
Compare
6807b05
to
8c91a81
Compare
8c91a81
to
5e6a19b
Compare
5e6a19b
to
21996a3
Compare
21996a3
to
2b97273
Compare
2b97273
to
69ed380
Compare
69ed380
to
3f047f9
Compare
3f047f9
to
19137cf
Compare
19137cf
to
71a65e1
Compare
71a65e1
to
e105818
Compare
e105818
to
9655f77
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.42.0
->3.48.0
Release Notes
jdbi/jdbi (org.jdbi:jdbi3-sqlobject)
v3.48.0
Compare Source
v3.47.0
Compare Source
@JdbiRepository
so aot generation works (#2727, thanks @hpoettker !)spring
module 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.0
Compare Source
v3.45.4
Compare Source
v3.45.3
Compare Source
v3.45.2
Compare Source
v3.45.1
Compare Source
v3.45.0
Compare Source
JdbiTestContainersExtension#setShutdownWaitTime(int)
to control waiting for extension shutdown if a database is very slow. Addresses #2629 (thanks @stoyants).v3.44.1
Compare Source
@Definition
feature also supports super-interface definitionsv3.44.0
Compare Source
@Definition
to 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
Compare Source
** 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: https://github.com/jdbi/jdbi/issues/2592
Optional
or vavrOption
(reported by @martyn0ff, #2558)fix SQL script parsing is (reported by @IrinaTerlizhenko, #2554).
integration-test
module for tests that require different parts of the code base. Should be used to write test cases for issue investigations.null
as a value for binding bean, method, field and pojo objects (Suggested by @xak2000 in #2562)ResultSet
fromCall
statements for databases that do not support cursor parameters. (suggested in #2557 by @metaforte and @0x1F528 in #2546)int
,long
,short
,double
andfloat
return values from out parameters directly.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.