View Single Post
  #8 (permalink)  
Old November 25th, 2011, 02:21 PM
Rod Stephens's Avatar
Rod Stephens Rod Stephens is offline
Wrox Author
Points: 3,166, Level: 23
Points: 3,166, Level: 23 Points: 3,166, Level: 23 Points: 3,166, Level: 23
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Jan 2006
Location: , , .
Posts: 647
Thanks: 2
Thanked 96 Times in 95 Posts

I think that would work in this example, although it doesn't quite feel "right" somehow.

In this example I'm assuming that all customers, vendors, and employees must have Persons records. If you don't require that, then you couldn't use one ID for everything because you might, for example, want to create a Customer without a Person.

But if you assume that all three must have Persons records, then I thikn it would work.

(I think the difference is mainly philosophical. In the design with separate IDs you're thinking about Customers, Vendors, and Employees and the Persons table provides extra detail for them. If you use the PersonId everywhere, then you're thinking about Persons and the Customers, Vendors, and Employees tables provide additional detail for them.)

Rod Stephens, Microsoft MVP

Essential Algorithms: A Practical Approach to Computer Algorithms

(Please post reviews at Amazon or wherever you shop!)