Wow.... :-) Let's look at this for what it is guys... it's no t hard to fix and there's no need to over-complicate the solution. That code exists simply because some JDBC drivers in the past did not like whitespace, so it was trimmed from all statements. Perhaps it's time (in 2009) to remove this code and let those drivers be updated if necessary, or let the users of those drivers write the unformatted SQL code. If this works, I'll add some code to the parser to remove newlines once in the build stage, so that it's not a runtime performance cost.
I've removed the formatting statements and committed the code to SVN. Please check it out, run the build and try it for yourselves to see if this solves the problem. Clinton On Tue, Feb 3, 2009 at 1:42 AM, Chema <demablo...@gmail.com> wrote: >> 2009/2/3 Clinton Begin <clinton.be...@gmail.com>: >> The statement cache operates only within a session/transaction scope, >> not between threads or users. So it would entirely depend on the >> overall approach. >> >> Clinton > > > Well, I supposed that all operation was made in the same thread (maybe > different transactions), with a loop. > But that only can be reply by Goodell > > By the way, one question : session scope != transaction scope , isn't it ? >
