Re: PostgreSQL Developer Best Practices - Mailing list pgsql-general

From Gavin Flower
Subject Re: PostgreSQL Developer Best Practices
Date
Msg-id 55DD069A.8000703@archidevsys.co.nz
Whole thread Raw
In response to Re: PostgreSQL Developer Best Practices  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: PostgreSQL Developer Best Practices
List pgsql-general
On 26/08/15 11:34, Adrian Klaver wrote:
[...]
>>>
>>> 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.
>>
>> DOH!
>>
>> Next time a screwball outfit sends you a check for $22k erroneously just
>> go deposit it :-)
>
> Well that is what I wanted to do, the owner overruled me:(. Something
> about Lowes having more lawyers then we did. The strange part was we
> called them and told them what had happened and supplied the relevant
> information that explained the mix up. You would have thought us
> calling to return a check that was supposed to be to us would have
> raised a flag!
[...]

Many years ago a department store credited our account with a refund for
about $150, which obviously was not meant for us - we had never bought
that item!

They replied, essentially saying we we were due the refund.

We sent a letter yet again, explaining the problem, and saying we were
not entitled.

They then sent used a check for the amount, which we cashed, feeling we
had done our best to help them & that we could not be bothered wasting
more time trying to sort things out for them!

I think any judge would laugh them out of court!




pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: PostgreSQL Developer Best Practices
Next
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL Developer Best Practices