"Anchor modeling" is not a database solution, at all.
Date: Sun, 5 Aug 2018 15:20:24 -0700 (PDT)
Message-ID: <80ee51f8-d87f-4fa0-915f-fb51d1a65bb5_at_googlegroups.com>
I will give one example so that professionals can see on real and important example, how bad "anchor modeling" is.
Example
People who are professionals in the business of databases, know that there
are thousands and thousands of international standards, which have been used
successfully in databases. All professionals know what is "VIN" for cars,
"ISBN" for books, and thousands of other international standards. Also, each
country has local standards for passports, personal documents, bank cards,
bar codes, etc
Many companies have their own standards. For example, when you pay
something, you have an invoice with a standard key written and that key is
written in the database, also.
This type of key from this example can be checked by a variety of institutions, police, customs, the bank can use your credit card, post offices, etc. You can check many of these "keys" on internet or by using a phone.
I believe that percent of these databases, which have entities with standard keys, and which I have presented in this example, is more than 95%.
For all the above cases the "anchor surrogate key" is nonsense. "Anchor modeling" exclusively uses "anchor-surrogate key"
In my solution, I use all the keys that are standard on a global or local level and are simple.
Vladimir Odrljin Received on Mon Aug 06 2018 - 00:20:24 CEST