[OT] What do you do with your SQL?

["Assenza, Chris" <ca...@Accessdc.com>]

Hi all, 

Been a while since I last wrote, but I've been lurking to observe all the
crazy antics. :)  Anyway, I've got a question of an [ot] nature that I
believe you folks will have an answer for. 

Our application is highly data-driven and as such a lot of our "business
logic" is written to build SQL statements and handle query results.  Pretty
typical stuff.  Using Struts we pass data objects to a stateless session EJB
where all the SQL is directly embedded into the java source one way or
another.  

We're currently converting this custom app into a product. As such, we need
to be able to have easily modifiable SQL statements without requiring
recompilation of code.  For example, if client A decides to buy our app and
they have xyz infrastructure or business rules, we need to be able to easily
modify sql, hints and the like while also supporting the client-specific
sql, hints, etc. of client B.  

A lot of our SQL is built on the fly so using properties files may be a
little cumbersome, though certainly not beyond our means.  I have other
ideas floating around, but I'd rather just hear yours - any suggestions? 

Thanks,

Chris


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>