Re: Q: Historical primary key

I would also like to mention that customer name is not a good static primary key.
People change their names all the time.

Diana Duncan
art2mis_at_apk.net

Barry Johnson <BJohnson_at_WorldBank.Org> wrote in article <32EF642F.A2E_at_WorldBank.Org>...
> Roger Wernersson (roger.wernersson_at_adra.se) wrote:
> > ...I want to be able to schedule
> > address changes...
> > ...I want a scheduleable phone number
> > table...
> > ...I am thinking about splitting
> > the
> > customer table into two, one containing static data and the other
> > containing dynamic data but it seems like all data is dynamic so it
> > would
> > look like this:
> >
> > CREATE TABLE customer (
> > name VARCAHR2 (20) NOT NULL,
> > PRIMARY KEY (name)
> > );
> >
> > CREATE TABLE customer_h (
> > customer VARCHAR2 (20) NOT NULL,
...
<rest deleted> Received on Sun Feb 02 1997 - 00:00:00 CST