Re: PostgreSQL Developer Best Practices

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL Developer Best Practices
Date: 2015-08-25 21:06:09
Message-ID: 55DCD8C1.1020906@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 08/25/2015 01:56 PM, John R Pierce wrote:
> On 8/25/2015 1:42 PM, Gavin Flower wrote:
>> Account numbers are externally generated, and may potentially change.
>> Management might suddenly decide that they want to start using the
>> year the account started as the first 4 digits, or that the branch
>> code should be reflected in it, or something else. The database
>> should be protected from these arbitrary changes. Hence the
>> account_no is not a good candidate for a primary key.
>
>
> such practices would raise total havoc on a traditional paper ledger
> accounting system as well as things like pending AR/AP where external
> companies will be referencing your account numbers.

Agreed, but it happens. When Lowes took over a local hardware
chain(Eagles) here in Washington state they moved very quickly on
changing the account numbers. The company I worked for who supplied
Eagles and then Lowes sat on a check for $22,000 that was sent to us in
error because the account numbers got switched. We called them when we
got the check, but it still took them six months to own up to it.

>
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gavin Flower 2015-08-25 21:23:13 Re: PostgreSQL Developer Best Practices
Previous Message John R Pierce 2015-08-25 20:56:48 Re: PostgreSQL Developer Best Practices