> person putting together the database doesn't understand
> normalization and doesn't care about performance. (sorry
> guys, but if you're seriously using FirstName, LastName, DOB,
> whatever fields as a compound PK, then you really need to
> hire a dba to work with you).
Actually, it's been my experience that you're quite likely to see a DBA
create a schema using compound fields as a natural primary key. This doesn't
have anything to do with normalization, and in fact one could make the
argument that the introduction of surrogate metadata is in fact a step
towards denormalization.
Personally, I strongly prefer surrogate keys, but this is actually still a
hotly-debated point in the database world. Joe Celko, for example, strongly
prefers natural keys. Googling on the string 'Celko "natural keys"' should
produce interesting reading.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
