xref table - design consideration

From: Barbara Baker <barbarabbaker_at_yahoo.com>
Date: Mon, 24 Nov 2003 09:44:25 -0800
Message-ID: <F001.005D7A00.20031124094425@fatcity.com>

List:
We're trying to design a CRM app. We believe we need 3 tables (Prospect/Customer, Private Party, and Agency) because those 3 kinds of (potential) customers have different attributes.

The sales rep should know whether they're looking up cust, private party, or agency. But what if they don't? (They're sales, after all. What if the have a hangover?) For performance reasons, we'd prefer not to join all 3 tables for a lookup.

I was thinking about 1 cross-reference table with the primary key from each of the 3 tables stored in one cross-ref table. Any way to keep such a table updated other than with a trigger?

Any other ideas about how to do a quick lookup without 1 big join?

In case you can't tell, db design is NOT my forte. Thanks for any ideas!

Barb

---

Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
--

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

Author: Barbara Baker
  INET: barbarabbaker_at_yahoo.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------

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 Nov 24 2003 - 11:44:25 CST