>> I did not mean an universal name for all tables, but a universal rule,
i. e. naming convention for the constraint name in order to avoid
something like PK_<table name> if there is a better solution/idea out
there. <<
I don't add a constraint name to a PK; it should stand by itself. But
my rules for getting a key are, in order:
1) look for an industry standard and use it. Some outside agency will
be doing all the hard work for you.
2) Look for a natural key. I.e. if you use (longitude, latitude) for
locations, you can buy a GPS to validate and verify it in the real
world.
3) Last desperate solution is to invent your own. That means
designing validation and verification, setting up a trusted source,
*****sing risk, etc. And then trying to get other people that share
data with you to use it, too.
|
