Dave Cramer wrote:
> No,
>
> What I was planning on doing is encapsulating all the code that parses
> the sql, and rewrites it into a small class, StatementSqlParser
> implement SqlParser, then changing the contstructor for
> AbstractJdbc1Statment to
>
> AbstractJdbc1Statement( Connection, SqlParser )
>
> Then I could create a second class CallableSqlParser which would deal
> with the differences in CallableStatements.
So essentially the SqlParser is a strategy object, or maybe strategy +
some state? Which object holds what state?
-O