From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | yanliang lei <msdnchina(at)163(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate |
Date: | 2023-08-19 19:39:12 |
Message-ID: | 63bed955-3353-5b1d-4855-2152c3cdf01e@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 8/18/23 15:57, yanliang lei wrote:
> Dear everyone,
> I raise this question based on the following considerations:
> 1. Make PostgreSQL easier for beginners to learn;
> 2. PostgreSQL is a database software product rather than a database software project. A product means being more user-friendly, precise, and reducing the likelihood of misunderstandings。
>
>
> The datetime type may make beginners think that there is a datetime data type in the PostgreSQL database. Although senior PostgreSQL professionals know that there is no datetime data type, the datetime type is enough to make beginners misunderstand.
> However, When they saw that the ReleaseNote in PostgreSQL 16 recorded "Accept the spelling"+infinity "in datetime type input",
> the term 'datetime type' is sufficient for beginners to misunderstand , unless it is noted that 'datetime type' is a general term, representing the following PostgreSQL data types: timestamp [(p)] [without time zone], timestamp [(p)] with time zone, date。
>
>
> I am not nitpicking ,I hope that: PostgreSQL database software products can become more perfect and accurate。
> Thanks a lot!
On the other hand, the standard talks about datetime types as a
collection of dates, times, timestamps, and intervals; and there is no
type called "datetime" in the standard. We are just doing the same
thing here.
--
Vik Fearing
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-08-19 23:57:29 | Re: BUG #18057: unaccent removes intentional spaces |
Previous Message | Tom Lane | 2023-08-19 17:19:22 | Re: BUG #18059: Unexpected error 25001 in stored procedure |