Search Postgresql Archives

Re: Any *real* reason to choose a natural, composite PK over a surrogate, simple PK?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



If one decides to use a composite key, beyond how many attributes
should one seriously consider creating a surrogate key instead? 4? 5?
Less? I have seen a composite key composed of 5 attributes and thought
- why? What's the value over a surrogate key?

I guess choosing a candidate key (presuming the candidates are
legitimate candidates) is at least partially a matter of taste. What
taste would compel people to choose composite keys composed of more
than 2-3 attributes?



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux