Tracy, where do you draw the line of when you should include
them in the table as atrributes?
Since new coverages could be added at any time, i'd make them
their own child entity.
I wouldnt concern yourself with i/o, if its indexed correctly
its so fast noawadays, i'm not sure you could tell the difference.
Anyone else's thoughts?
Joe
>>> [EMAIL PROTECTED] 06/25/01 01:15PM >>> 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: [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). |
- Design Question - Thoughts Needed Tracy Rahmlow
- RE: Design Question - Thoughts Needed JOE TESTA
- RE: Design Question - Thoughts Needed Mercadante, Thomas F
- RE: Design Question - Thoughts Needed Toepke, Kevin M
- Re: Design Question - Thoughts Needed Big Planet
- RE: Design Question - Thoughts Needed Christopher Spence
- RE: Design Question - Thoughts Needed Tracy Rahmlow
- RE: Design Question - Thoughts Needed Tracy Rahmlow
- RE: Design Question - Thoughts Needed Mercadante, Thomas F