Re:surrogate keys (was: Seeking Database Design Guide)

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

>Buck Calabro wrote:
>> 
><snip>
>
>> Has anyone here used "surrogate keys" for their files?
><more snipping>
>
>> Now, given the same mistake, it's easy to simply swap the employee
>> numbers because the surrogate keys are different for each employee..
>> 
>I take it that your transaction file or some daily totals files is
>indexed by employee/date and do not allow for duplicates.  Surrogate
>keys would not solve the issue since you would then have to have the
>logic in the application to deal with multiple entries per
>employee/date.  If it can do that then you can change the index to allow
>for duplicates, retain the multiple logic and forget the surrogate..

You're right, of course.  I was trying to find a simple enough example
and made a poor choice.  This is something that out Synon folks are
trying out; it's a new concept for me...  Nevertheless, the "duplicate
key" issue is one of the major selling points (or so I am told<g>)
I understand thta other databases use surrogate keys under the
covers...(MS Access for one)

Buck Calabro
Commsoft

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *