I'd like to move all of that stuff into it's own class, as the rest of
my patch ends up with alot of if( instanceof CallableStatement) which
I'd like to avoid by putting it all in a CallableStatement
implementation.
Thoughts?
--dc--
On Fri, 2004-06-18 at 20:21, Oliver Jowett wrote:
> Dave Cramer wrote:
> > See Kris's addition.
> >
> > At this point however I've done some work and realized that most of the
> > parsing, binding and rewriting of the queries will need to be
> > encapsulated in two classes, one for regular statements, and one for
> > callable statements. This will allow me to totally encapsulate the logic
> > for this inside the CallableStatement implementations, instead of
> > mucking up the current AbstractJdbc1Statement code.
>
> You might want to look at my pending patch first -- I've overhauled
> modifyJdbcCall and added a method that translates between user-provided
> parameter indexes and actual query parameter indexes that sounds like
> it'd be useful for this case.
>
> -O
>
>
>
> !DSPAM:40d386ac236762102998748!
>
>
--
Dave Cramer
519 939 0336
ICQ # 14675561