Re: A general questio about names
Date: 9 Sep 2005 05:42:46 -0700
Message-ID: <1126269766.670799.239750_at_z14g2000cwz.googlegroups.com>
John G. Eggert wrote:
> I'm in the process of attempting to lay out a general overview of what a
> properly set up database would look like for my current employer. My question
> is with respect to names.
>
> I seem to see at least 3 types of proper names that are independant
> and have different issues. Employees, who have employee numbers and a SIN
> (SSN for our American friends and apologies to the rest of the world). The
> SIN seems like the appropriate primary key. Some employees leave and then
> return and may have a different employee number. The second name is for
> vendors who would require an artificial key. I can't imagine asking someone
> selling me stuff to give me a SIN because I can't design a database without
> one. This seems to imply that I need at least three separate tables. The
> first for employee names, second for vendors, third for prospective
> employees (no SIN yet, but if they become employees, it will become known,
> etc. Prospective employees have no obligation and employers no right to
> demand the SIN. I suspect though haven't checked that it is an offence to
> demand the SIN except under very specific conditions. Application for
> employment is NOT one of them)
>
> Alternately, I can set up a single table for 'name'. In this case I would
> need an artificial key, such as name#. The key would then be generated by some
> sub program that assures it is unique. I notice that this is the route taken
> by Date, though whether this is authoritative is beyond me.