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

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Single Code Table or Separate Code tables dilemma

Re: Single Code Table or Separate Code tables dilemma

From: Kresimir Fabijanic <kresimir_at_ozemail.com.au>
Date: Fri, 23 Mar 2001 05:14:07 -0800
Message-ID: <F001.002D5D41.20010323044524@fatcity.com>

Mandar

Tell them that (if they are really lazy) you can build them a function that returns ref cursor with Code, description columns and they pass in the domain/context they want - same for the inserts - so you can get rid of their comments. To be sincere, I use combination - separate look-up tables for the entity related types, statuses etc and one for generic stuff like boolean i.e. if site uses 1,0 or Y/N or TRUE/FALSE and date/time formats etc. which does not map to any particular entity/object.

HTH Regards

Kresimir Fabijanic

--

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

Author: Kresimir Fabijanic
  INET: kresimir_at_ozemail.com.au

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 Fri Mar 23 2001 - 07:14:07 CST

Original text of this message

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