CallableStatement and parameterName

[Moody Hopkins]

How do you use the CallableStatement and parameterNames?
I do not want to use the indexes (indi?) and wildcards if possible.
I know how to use the ? type statements.
I would like to use these type of "setX" methods:
setString(String parameterName, String x)
instead of the :
setString(int parameterIndex, String x)
type methods.
Is this possible? If so, how do I create the statement?
Thanks!!!

[Jeanne Boyarsky]

Moody,
There is a good article on this. Basically the names of the parameters need to match the names declared in your stored procedure.

[Loren Rosen]

Oracle supports precisely what you want, if you use OracleCallableStatement. That, of course, is specific to Oracle, but I think the technique described in the article Jeanne mentions is also Oracle-specific.

[Moody Hopkins]

Thank you very much for the link! However, after reading the article, it seems that it still uses the positional notation. The only difference is the parameters are named in the stored procedure. The java code still has to know the order of the parameters. This is what I would like to avoid.
Perhaps this is not possible? But it must be, why else do we have the functions overidden with named parameters?
What I would like to do is avoid the ? thing altogether.
Thanks!

[Jeanne Boyarsky]

Moody,
In this code from the article, it shows how you are defining the order in your java code. While you still set the parameters using indexes, these numbers are based on the order set in the java code. So if you wanted p_status to be #1, you would put it first.

sbQuery.append( "{call mytest( p_msisdn => ?" );
sbQuery.append( ", p_message => ?" );
sbQuery.append( ", p_status => ?" );