M
marian.edu
Guest
I'm a bit confused by the fact you're mixing triggers with stored procedures but anyway you might go down a slippery road here by keeping business logic in your database since while calling stored procedures through JDBC/ODBC is a standard the language used to implement those is vendor specific. So say you rewrite the business logic code from 4GL to stored procedures/triggers for OE RDBMS then when you move to another database engine you will have to do that again so why bother with the intermediate step? If the only thing that stops you from moving to hibernate for the business logic is the fact that the 4GL triggers does not fire when you connect through JDBC then the driver mentioned before could help since that is using the 4GL database engine so the 4GL triggers fires just fine. This does require an application server though so if that is not available already acquiring more OE licenses in the interim might not be the best solution although you probably still need to support the 4GL version for a while and the migration won't just happen over night. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Continue reading...