Using procedures instead of coding update/insert SQL...huh?

From: Grabowy, Chris <cgrabowy_at_fcg.com>
Date: Mon, 14 Jan 2002 07:58:16 -0800
Message-ID: <F001.003EF19E.20020114071021@fatcity.com>

I just joined a new Oracle/Java project using Tomcat app server. On this project they decided to create an update procedure and insert procedure for every table. This procedure is then called in the Java code with the appropriate parameters passed, instead of simply coding the UPDATE or INSERT SQL directly in Java.

Does anyone else take this approach? I'm trying to understand the pros vs cons of this approach.

TIA!!! Chris
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Grabowy, Chris
  INET: cgrabowy_at_fcg.com

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: ListGuru_at_fatcity.com (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). Received on Mon Jan 14 2002 - 09:58:16 CST