Is your feature request related to a problem? Please describe.execute-batch! requires users to create a PreparedStatement themselves which made sense when it was in next.jdbc.prepare but makes less sense now there's a version in next.jdbc.
Describe the solution you'd likenext.jdbc/execute-batch! should accept the same types of DB references that execute! et al take -- preferably by extending the protocol to include some version of execute-batch!.
Describe alternatives you've considered
The top-level function could dynamically test the argument type. A new wrapper could be added. The documentation could just show how to call next.jdbc/prepare and then next.jdbc/execute-batch!.
Caveat: make sure extending the protocol is not a breaking change!
Is your feature request related to a problem? Please describe.
execute-batch!requires users to create aPreparedStatementthemselves which made sense when it was innext.jdbc.preparebut makes less sense now there's a version innext.jdbc.Describe the solution you'd like
next.jdbc/execute-batch!should accept the same types of DB references thatexecute!et al take -- preferably by extending the protocol to include some version ofexecute-batch!.Describe alternatives you've considered The top-level function could dynamically test the argument type. A new wrapper could be added. The documentation could just show how to call
next.jdbc/prepareand thennext.jdbc/execute-batch!.Caveat: make sure extending the protocol is not a breaking change!