Steven Schlansker

Unfortunately they are currently mutually exclusive. It might be possible to get them to play nicely together, but I think unfortunately this is a new feature request, not something that...

More specifically: row reducers happen *instead* of normal mapping rules.

So, this stuff is pretty confusing, but my understanding is that the `isAccessible` method is deprecated but that `setAccessible` isn't actually deprecated. What is deprecated is using it _across modules_...

Thank you for the suggestion @uschindler . I agree, making it configurable and potentially changing the default later would be a good path.

We'd already talked about making it configurable. Instead of calling `setAccessible`, we could provide an extension point, possibly a `Consumer`. The default could continue to call `setAccessible` as today, with...

Very nice. The qualified type approach is more suitable if we really want to think about non-null values as a totally separate type. I think this leads to additional complexity...

For library `Result` types, you're encouraged to add a simple `ResultMapperFactory` to your own application - you can look at the standard `OptionalMapperFactory` for some ideas on how to implement...

Another thought regarding the original question: the feature request as is is reasonable, but Jdbi will not in the long run be getting extensive validation facilities. If you're trying to...

This happens when Jdbi cannot determine the (erased) type that is bound. Unless you provide us type information (like `bindByType` or using `SqlObject` methods) all we know is that a...

Yes, could you please provide additional details: what database, what database driver, and versions? Does retrieving the generated keys work as expected if you use vanilla JDBC? We do have...