Juha Komulainen

Sounds like a good idea. Currently there's no way to customize this, but this is the only place in Dalesbred's code that deals with ResultSets so it should be a...

Thanks for the suggestion. I've thought about this along the same lines, so I'm open to the idea. I have some concerns though: nobody reads documentation and I'm afraid people...

Hi! Sorry for the delayed answer. Currently there's no support for interceptors at the statement level. If you implement your own [`TransactionManager`](http://dalesbred.org/docs/api/org/dalesbred/transaction/TransactionManager.html), Dalesbred will call either [`withCurrentTransaction`](http://dalesbred.org/docs/api/org/dalesbred/transaction/TransactionManager.html#withCurrentTransaction-org.dalesbred.transaction.TransactionCallback-org.dalesbred.dialect.Dialect-) or [`withTransaction`](http://dalesbred.org/docs/api/org/dalesbred/transaction/TransactionManager.html#withTransaction-org.dalesbred.transaction.TransactionSettings-org.dalesbred.transaction.TransactionCallback-org.dalesbred.dialect.Dialect-) whenever...

OK, then you might be happy to find out that Dalesbred already [logs all queries](https://github.com/EvidentSolutions/dalesbred/blob/master/dalesbred/src/main/java/org/dalesbred/Database.java#L681). You just have to bump up the log level of `org.dalesbred.Database`-category. Dalesbred logs using `java.util.logging`...

Right, I suspected something like this. This is not prettiest solution, but you should be able to write your own [java.util.logging.Handler](https://docs.oracle.com/javase/8/docs/api/java/util/logging/Handler.html) to get callbacks whenever Dalesbred logs the queries. You...

I got a bug report from a user of my library saying that exceptions are not printed correctly and after some investigation found this bug. The offending line in my...

Right, this seems like a reasonable enhancement. I think supporting just `text/plain` is a good start with obvious implementation, but this could even be enhanced to support other types in...

Hi, thanks for your feedback! You're right, there's no special support at the moment. You can of course call `catchError` on the returned `Observable` or pass error-handler to `subscribe`, but...

It seems that at the very least Apina could provide two things: 1. Allow registering some Java-types as needing serialization support even though they are not needed in request/response bodies....

If Apina would provide a manual API serialiation-api, you could implement second option as easily as you could configure it. Say that you know that every response has an `errorCode`...