From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Is this a bug ? |
Date: | 2019-10-23 18:55:43 |
Message-ID: | e29a32ed-4f56-91a4-791c-cf96695fa64d@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/23/19 11:20 AM, Geoff Winkless wrote:
> On Wed, 23 Oct 2019 at 17:09, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>
>> As much as I hate to say it, MSFT was right to ignore this bug in the standard.
> Standards are standards for a reason. It is almost never correct to
> deliberately ignore them. If you don't like them, then revise the
> standard.
>
> Historically Microsoft ignored standards either because they
> misunderstood them or because they wanted to lock in their customers,
> not for any reasons of altruism.
>
> For what it's worth, I can see a value to having
>
> SELECT 'this is quite a long string'
> 'which I've joined together '
> 'across multiple lines';
>
> although the advantage of it vs using a concat operator is slim.
It just occurred to me that this is probably something that COBOL does (it's
been 30 years, so I might be mistaken) and so that's how it slipped into the
SQL standard.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Stuart McGraw | 2019-10-23 19:00:47 | Re: jsonb_set() strictness considered harmful to data |
Previous Message | Peter J. Holzer | 2019-10-23 18:33:06 | Re: jsonb_set() strictness considered harmful to data |