Re: Oracle and PICK

In message <RMZgc.51742$aD.38523_at_edtnps89>, Dale Benedict <dalebnospam_at_spamnotwantedflightcraft.ca> writes
>The invoice information, billing, ship-to, and all order lines containing,
>part numbers, quantity for each part, cost at invoice time, retail amount
>billed at invoice time etc. Read such a record and most of the required
>information is already read. There is no need to look up into a
>invoice-line number table to retrieve all the invoice line information. In
>Pick all that may be left to do is to look into the parts inventory table to
>retrieve a description. Heck, even the description at the time if invoicing
>may want to be saved just in case the powers that be insist on recreating
>the invoice exactly at some later date.

Actually, the "description at the time" should be stored somehow (maybe make the lookup-table entries immutable) otherwise you can't recreate a copy of the invoice.

Actually, that sort of mistake is something I would suspect was more typical of a novice relational analyst, not a Pick one. You're making me question that :-)

Cheers,
Wol

-- 
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
HEX wondered how much he should tell the Wizards. He felt it would not be a
good idea to burden them with too much input. Hex always thought of his reports
as Lies-to-People.
The Science of Discworld : (c) Terry Pratchett 1999