Steven Schlansker
Steven Schlansker
Closing as answered, we can re-open if there's more followup.
@anborg , the Jdbi project is not trying to be anti-reactive here, but we do want to make sure that accepting reactive compatibility does not completely upend the project. The...
Hi @ngohuybach @RamonaBarbieru , did you see the update in https://github.com/jdbi/jdbi/issues/2411 this is probably because once the statement returns, the OutParam is closed. Take a look at the linked example...
@mieseprem , please check out #2304 and see if that helps you
Thank you! Yes, we'd be happy to accept additional tests that verify DB2 and in particular returning `byte[]`. We would probably mark it as a "slow" test since it takes...
If this feature is important to you, please consider contributing a fix! We always welcome well thought out contributions. Extra points are awarded for improving the documentation and having good...
The latest jdbi 3 versions will work in any supported JDK. (11, 17, 20 right now)
Return type of setters shouldn't be important, however the name surely is. Can you post a sample case that fails? We could possibly improve the behavior. I think allowing `chain=true`...
Either a new mapper, or maybe preferably extend the existing reflection mappers to also find fluent style properties. At the end of the day it feels like there is one...
We ended up removing all uses of bytebuddy agent and only using Mockito in Proxy mode for pure interfaces (to make java 22 migration easier, and a lot of those...