home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!bogus.sura.net!howland.reston.ans.net!usc!cs.utexas.edu!uwm.edu!ogicse!news.u.washington.edu!byron.u.washington.edu!sandahl
- From: sandahl@byron.u.washington.edu (Bonnie Sandahl)
- Newsgroups: comp.databases.theory
- Subject: - Normalization - Naming Conventions Question -
- Message-ID: <1iv0tmINNafn@shelley.u.washington.edu>
- Date: 12 Jan 93 17:59:18 GMT
- Article-I.D.: shelley.1iv0tmINNafn
- Reply-To: sandahl@u.washington.edu
- Distribution: world
- Organization: University of Washington, Seattle
- Lines: 17
- NNTP-Posting-Host: byron.u.washington.edu
-
-
- I have a question involving database normalization. Let's say you create a
- CUSTOMER table for Accounts Receivable with CUSTOMER-NO as the
- primary key. Let's go on and say that you have a VENDOR table for Accounts
- Payable with VENDOR-NO as the primary key.
-
- Suppose you have a high percentage of customers that could also be vendors
- and you didn't wish to keep separate tables. You decided to create a table
- called CUSTVEND with primary key CUSTVEND-NO that would have all entities
- that could be customers or vendors.
-
- In the Accounts Receivable system when you set up an INVOICE table, would
- you call the key attribute CUSTVEND-NO or CUSTOMER-NO? Similarly, in the
- Accounts Payable system when you set up a PAYABLE table would you call
- the key attribute CUSTVEND-NO or VENDOR-NO?
-
- Thanks - sandahl@byron.u.washington.edu
-