You make DZone different! Login and vote now.
In previous paper we were considering the duplicate rows problem resolving, caused by lack of a primary key. Now let consider more difficult case, when key is present but it is synthetic. When design is improper it can lead to duplicate rows appearing, from a subject area view point.
It is strange, but even if I am tell to my students about synthetic primary key disadvantages, they are still use ones in their first data base projects. Probably all people need to enumerate everything :)
Comments
dcortez replied ago:
SMMS replied ago:
2dcortez
I have understood it so, that you the adherent of synthetic keys. :-)
chase.saunders replied ago:
There are cases where I use a synthetic key as a primary key, and additionally define a natural key of some kind (e.g. via a unique index). That seems to avoid the problems the author cites with synthetic keys. That said, it is a kind of treatise on how to clean up a database in which the keys have been abused (or why you wouldn't want to).
lil replied ago:
thanks for useful articles.
SMMS replied ago:
2chase.saunders
> and additionally define a natural key of some kind (e.g. via a unique index).
Just about it I also wrote.
Voters For This Link (15)
Voters Against This Link (1)