Our Java users are concerned that there may be a possibility that their code
may have to work on top of a variety of databases. We use Oracle in-house
but we, theoretically, may sell our product to another company that uses
something else besides Oracle. Our product would then have to talk with
their database. What, then, are the advantages and disadvantages of using
views, procedures, triggers, etc. What would buy us the most portability?
What headaches might we just have to deal with because there is no way
around it?
Any insights would be greatly welcomed. Feel free to email me privately at
[EMAIL PROTECTED]
Thanks!
Linda
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Seley, Linda
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
