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: Design Question - Thoughts Needed

RE: Design Question - Thoughts Needed

From: Christopher Spence <cspence_at_FuelSpot.com>
Date: Mon, 25 Jun 2001 11:51:49 -0700
Message-ID: <F001.00337014.20010625115338@fatcity.com>

I would have a three table set up.

Your policy detail table, your vehicle table, and your vehicle_policy lookup table.
I generally use this format to resolve many to many. Most of the time you either know the vehicle or policy type. Which will keep you in the lookup table and only go to the appropriate records in the parent table.

"Walking on water and developing software from a specification are easy if both are frozen."

Christopher R. Spence
Oracle DBA
Fuelspot

-----Original Message-----
Sent: Monday, June 25, 2001 1:16 PM
To: Multiple recipients of list ORACLE-L

We are looking to redesign our current system and a question popped up that I
am struggling with. (our business is auto insurance). Each vehicle on a policy may have 1 or many coverages. For example, comprehensive, collision,
towing, property damage ... A couple of things: 1- some coverages will not apply because they are state specific. 2 - some coverages will not be chosen
by the insured. Therefore, should I have a vehicle table with each coverage and its premium as separate specific columns or should I add a coverage table
which will contain the coverage and premium. Under the later example if I have
10 coverages and I want to print them on the insured's declaration page don't I
have a possible performance problem with up to 10 i/os. Where as with the first example I only have 1 read but possible space wastage. I know in 1st normal form you should remove repeating groups, in my case is a coverage a repeating group? Where do you draw the line? For example, clients may have
multiple phone numbers although I don't see many examples where the phone numbers are split into another table. Please share any thoughts that may make
my decision easier. Thanks

Just an fyi, in our current design the coverages have been stored with the vehicle.

--

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

Author: Tracy Rahmlow
  INET: Tracy.Rahmlow_at_aexp.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).
--

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

Author: Christopher Spence
  INET: cspence_at_FuelSpot.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 Jun 25 2001 - 13:51:49 CDT

Original text of this message

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