Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> OO design question

OO design question

From: Jim Lynch <jwl_at_sgi.com>
Date: Tue, 26 Feb 2002 14:41:36 -0500
Message-ID: <3C7BE4EF.87F103BC@sgi.com>


I'm starting to get involved with Java and Oracle and have pondered this question before but never really liked my answers. Assuming you're going to do a number of database actions, multiple selects, updates, inserts, etc. on a database, does it make any sense to define a class to interact with the database to isolate DB activity to a single class or would you simply form the queries, etc. in each of the classes as you need them? Isolating them seems to make sense, but then it would be more difficult to read the code I would think. I'm leaning toward doing it that way, generating a method for each of the various actions I need to perform and, hopefully documenting them so it will be evident what is happening.

Any other ideas?

Thanks,
Jim. Received on Tue Feb 26 2002 - 13:41:36 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US