commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raymond DeCampo <>
Subject Re: [dbutils] OUT parameters for stored procedures (DBUTILS-50, DBUTILS-104)
Date Mon, 01 Sep 2014 15:24:34 GMT
Sorry, somehow I managed to send the message before I finished typing it up.

In any case, CallableStatementHandler would extend ResultSetHandler and be
used in a similar fashion.  There would be methods for registering the OUT
parameters and then retrieving their values.  Then I would add methods to
QueryRunner mirroring the current query() methods but accepting a
CallableStatementHandler instead.

After reading DBUTILS-50 however, I'm not sure if this is the solution
desired by the team.  Let me know if it is worth continuing in this
direction, or if another approach is preferable.


On Mon, Sep 1, 2014 at 11:19 AM, Raymond DeCampo <> wrote:

> I was hoping to contribute a solution to these issues for the dbutils
> project.  If I am not mistaken, DBUTILS-104 is a duplicate of DBUTILS-50.
>  Both request means of running stored procedures and retrieving the values
> of OUT parameters.
> At first I only noticed DBUTILS-104 and started coding up a solution based
> on adding methods to QueryRunner along with a new CallableStatementHandler
> interface with methods for registering the

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message