Kazuhiro Sera

Ah, you’re right

Although I've considered supporting CallableStatement before, I've not figured out what the best API design is. Related issues: - https://github.com/scalikejdbc/scalikejdbc/issues/59 CallableStatement support - https://github.com/scalikejdbc/scalikejdbc/issues/380 callable statements API: Need to be...

Yeah, that's right. I meant having realistic test cases will help us to make the API design mature.

@VEINHORN To be honest, I'm not in a hurry because I myself have less opportunities to use CallableStatement at least now. So I have no confidence about its appropriate API...

This is still an open issue. I myself do not have the bandwidth to work on this feature in the short term but contributions are welcome. If you are interested...

I am not planning to take action for this in the short term but if someone has thoughts or inputs on this issue, please share the knowledge with the community!

If having a new option like `GlobalSettings.setReadOnlyDisabled`, which is similar to `jtaDataSourceCompatible` but it does not do anything for `autoCommit`, may be helpful for the following JDBC driver users: *...

Thank you for your feedback. Although we don't have a plan to add read-only transaction support right now, I will consider adding it if there are many demands.

Hey @sh0hei, thanks for suggesting this! I think either apply method or constructor should work in this scenario and perhaps, changing this is okay. Do you have a specific issue...

I'll release v4.0.0 shortly and after that, the `master` branch will be for v4.1 development. If you are still happy to work on this PR, let us know 👋