Re: date_part/extract parse curiosity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Japin Li <japinli(at)hotmail(dot)com>
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: date_part/extract parse curiosity
Date: 2022-10-20 14:12:05
Message-ID: 3036877.1666275125@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Japin Li <japinli(at)hotmail(dot)com> writes:
> On Thu, 20 Oct 2022 at 20:45, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
>> I noticed that
>> select date_part('millennium', now()); --> 3
>>
>> will execute also, unperturbed, in this form:
>> select date_part('millennium xxxxx', now()); --> 3

> Maybe we should document this. I'd be inclined to change the code to
> match the certain valid field names.

I think changing this behavior has a significant chance of drawing
complaints and zero chance of making anyone happier.

The current state of affairs (including the lack of unnecessary
documentation detail) is likely quite intentional.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-10-20 14:17:54 Re: ccache, MSVC, and meson
Previous Message Japin Li 2022-10-20 13:57:34 Re: date_part/extract parse curiosity