Issue 'TRQ6' has just been modified by user 'stephenh'
You can view the issue detail at the following URL:
<http://scarab.werken.com/issues/id/TRQ6>
The following modifications were made to this issue:
I like the idea of getting rid of the adapters, but I feel it might be a bit too
idealistic. Even with JDBC and what not, any time we generate strings of SQL, there
will be variations from db to db.
Though perhaps JDBC 3.x has (or should have) some way in the API of getting around
using any raw SQL text and instead use API method calls with each driver taking the
burden of building the db-specific SQL?
What do I think we should do in the short term is get rid of all of the db.props files
and move them into their respective adapters as static constants. Then put a Velocity
static-field-wrapper instance into the context for the templates to use.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
