--- "Joshua D. Drake" <jd@xxxxxxxxxxxxxxxxx> wrote: > The value of a surrogate key is easy retrieval and really has nothing to > do with normalization or proper modeling. > > I often add a surrogate key, even when one is not required just so I > don't have to worry about have a 4 element where clause. I've often wondered about this. Since PostgreSQL allows FOREIGN KEYS to be referenced from UNIQUE (non-primary) natural keys, couldn't the schema be designed so that every table has a surrogate PRIMARY KEY and yet still maintain the relationships using UNIQUE natural keys. Would a design like this be practical? Regards, Richard Broersma Jr.
