Re: Use IDs or strings?

Walter Mitty wrote:

If so, it is better to plan and design such ID's rather than just
exposing a sequence number value. A VIN (Vehicle Identification
Number) is a good example. It isn't perfect, but it goes a long way
beyond just a number.
Ed

Elsewhere, it's been said that a key should NOT carry any information beyond identifying something. You seem to be saying the opposite. Am I reading you right?

Of course.

Mr. Elsewhere is wrong.

The following links just scratch the issue. I suppose it's been going on for more than 20 years.

http://it.toolbox.com/blogs/database-soup/primary-keyvil-part-i-7327
http://it.toolbox.com/blogs/database-soup/primary-keyvil-part-ii-7345
http://it.toolbox.com/blogs/database-soup/primary-keyvil-part-iii-7365
.

Relevant Pages

  • Re: Use IDs or strings?
    ... exposing a sequence number value. ... A VIN (Vehicle Identification ... The first article makes my point. ...
    (comp.databases)
  • Re: VIN Numbers
    ... Current snowmobiles have a 17 digit Vehicle Identification Number (VIN). ... Digits 4-9: Vehicle ... engine type, and series. ...
    (rec.sport.snowmobiles)
  • Re: Toyotas plants
    ... So do Japan, England, and Australia also have "VIN" laws ... (VIN or Vehicle Identification ... How about a law similar to our Origin Sticker ...
    (alt.autos.toyota)
  • Re: Use IDs or strings?
    ... A VIN (Vehicle Identification ... The first is surrogate keys vs. natural ... There is a place where composite keys are worthwhile: ...
    (comp.databases)
  • Select query numbering results
    ... I have repair records which list Repair Date,Repair Order number, VIN ... Each repair order may contain up ... If I had the sequence number I could write the data to a table and then ...
    (microsoft.public.access.gettingstarted)