Re: Is this a bug ?

From: Fabio Ugo Venchiarutti <f(dot)venchiarutti(at)ocado(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>, "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:51:16
Message-ID: d5a3175c-a275-c02a-1a31-42b2dcafb802@ocado.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 23/10/2019 17:30, Ron wrote:
> On 10/23/19 11:27 AM, Geoff Winkless wrote:
>> On Wed, 23 Oct 2019 at 17:20, Geoff Winkless <pgsqladmin(at)geoff(dot)dj> wrote:
>>> 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.
>> As an aside, Postgres isn't the only DB to follow the standard here.
>>
>> mysql> select 'hello'
>>      -> ' there';
>> +-------------+
>> | hello       |
>> +-------------+
>> | hello there |
>> +-------------+
>
> This is the kind of weird stuff that we mocked mysql for.
>
> This too would have been roundly mocked if discovered in mysql:
>
> postgres=# select to_date('2018150X','YYYYMMDD');
>   to_date
> ------------
>  2019-03-03
> (1 row)
>
>

The main difference being that we mocked MySQL because it BROKE the
standard requirements in bespoke, arguably lazy/stupid/dangerous ways
(and often undocumented as a result).

You ran into a gotcha of the SQL specification; in your shoes I'd
instead appreciate the fact that the PG maintainers went out of their
way and documented this spec weirdness as such in their own project when
they could have just went "look into the specification for oddities".

MySQL silently truncated your overflowing string for years without as
much as a warning, by default. In my book that broke specification, rule
of least surprise, data safety and a lot more.

--
Regards

Fabio Ugo Venchiarutti
OSPCFC Network Engineering Dpt.
Ocado Technology

--

Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this message
may not necessarily reflect the opinions and views of the members of the
Ocado Group.

If you are not the intended recipient, please notify us
immediately and delete all copies of this message. Please note that it is
your responsibility to scan this message for viruses.

References to the
"Ocado Group" are to Ocado Group plc (registered in England and Wales with
number 7098618) and its subsidiary undertakings (as that expression is
defined in the Companies Act 2006) from time to time. The registered office
of Ocado Group plc is Buildings One & Two, Trident Place, Mosquito Way,
Hatfield, Hertfordshire, AL10 9UL.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2019-10-23 18:33:06 Re: jsonb_set() strictness considered harmful to data
Previous Message Adrian Klaver 2019-10-23 16:40:20 Re: Is this a bug ?