|
From: Tom T. <tom...@pr...> - 2004-06-03 22:07:40
|
Hi Juergen! > Basically, you're bypassing all of SqlOperation's functionality when you > use a custom PreparedStatementCreatorFactory. That's why I considered it > a bug that "newPreparedStatementCreator" wasn't final before. True, but I don't actually want to use a custom one, I just want to customize the existing one a bit ;-) Thomas' suggestion sounds like a good idea! > wasn't a particular good idea to change that at this point of time, > though - sorry for any inconvenience. Never mind, I should have tested the cvs version before 1.0.2 was released [shamefaced smiley here] ;-) > What you can do is perform the query yourself rather than delegating to > SqlQuery's execute method: Hmm, wouldn't that be bypassing all of SqlQuery's functionality, essentially? ;-) As I'm also using a custom ResultReader (with range support), I can probably just as well extend from RdbmsOperation directly... Thanks for the suggestions! Tom. |