| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Is this a bug ? |
| Date: | 2019-10-23 16:20:07 |
| Message-ID: | CAEzk6fejkodG2RCY9kjeD=a+X9+-iD4h5tSL576n529rNwFs8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2019-10-23 16:27:12 | Re: Is this a bug ? |
| Previous Message | Maciek Sakrejda | 2019-10-23 16:13:08 | Re: EXPLAIN BUFFERS and I/O timing accounting questions |