Re: pervasiveness of surrogate (also called synthetic) keys - Mailing list pgsql-general

From Misa Simic
Subject Re: pervasiveness of surrogate (also called synthetic) keys
Date
Msg-id BANLkTikcZpcH_kQ-_6j_DZNQqMwaJDGHrg@mail.gmail.com
Whole thread Raw
In response to Re: pervasiveness of surrogate (also called synthetic) keys  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: pervasiveness of surrogate (also called synthetic) keys  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-general


2011/4/28 Merlin Moncure <mmoncure@gmail.com>
On Thu, Apr 28, 2011 at 12:29 PM, Jim Irrer <irrer@umich.edu> wrote:
*) most tables don't have unique natural keys (let's see em)
etc


i.e for an Invoice, we have at least 2 tables (more in practice...):

Invoice Header
    -Invoice Number
    -Date
    -CustomerID
    -Currency

Invoice Line
    -ItemID
    -qty
    -Price


This is not real design for tables, just basic real info stored to represent 1 Invoice Document.

Now, let say for Invoice Header, "Natural" PK is Invoice Number, so we will add that column to Invoice Line table as FK....

What should be "Natural" PK for Invoice Line table?

Also, if we now add additional tables i.e. Serial Numbers, related to Invoice Line, what should be "Natural" key in it?

Thanks,

Misa

pgsql-general by date:

Previous
From: Sim Zacks
Date:
Subject: Re: multiple group by on same table
Next
From: Gabriele Bartolini
Date:
Subject: Re: multiple group by on same table