insert column monetary type ver 2

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: insert column monetary type ver 2
Date: 2021-11-22 02:43:22
Message-ID: CAKFQuwaoNoeU0m9FSZNm2ag7eBMA+p8QD8O7CNvAR0i-uTH4kQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sunday, November 21, 2021, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:

> On 11/21/21 7:33 PM, Adrian Klaver wrote:
>
>> On 11/21/21 17:08, Ron wrote:
>>
>>> On 11/21/21 10:27 AM, Tom Lane wrote:
>>>
>>>> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>>>>
>>>
>> The contrary argument is that people tend not to like "best guess"
>>>> behavior when working with monetary amounts.
>>>>
>>>
>>> Best Guess is relative. Breaking because of "ASCII Space" instead of
>>> "narrow no-break space" is definitely Not Right.
>>>
>>
>> The people I have worked for have forgiven me many sins, messing up the
>> money is not one of them.
>>
>
> Not inserting this record is also messing up the money.
>
>
Adding processing smarts here is Not Definitely Right. And the status quo
is Not Definitely Wrong. As long as we don’t have a round-trip problem I’d
lean toward maintaining the status quo and accept the complaints that we
aren’t being as flexible as we could be with our money type. That we
interpret the LC setting exactly is a defensible position to take.
Especially since money is a type we advise people avoid anyway. We can
just add this to the list of reasons why.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2021-11-22 03:21:53 Re: insert column monetary type ver 2
Previous Message Ron 2021-11-22 02:15:46 Re: insert column monetary type ver 2