| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | adh(at)sanger(dot)ac(dot)uk, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Ambiguous language in Table 8.13. Special Date/Time Inputs |
| Date: | 2019-07-09 03:32:34 |
| Message-ID: | 20190709033234.ytbltfn25h5wvdbd@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Jul 8, 2019 at 10:07:59AM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/datatype-datetime.html
> Description:
>
> In Table 8.13. Special Date/Time Inputs, the description for the special
> values 'today', 'tomorrow' and 'yesterday' uses the word 'midnight' e.g. the
> special value 'today' is defined as 'midnight today'. I propose that the
> word 'midnight' is ambiguous, because it can be interpreted either as
> midnight at the start of the day in question, or midnight at the end of the
> day. This ambiguity can be avoided if 'midnight' is replaced by '00:00:00',
> or better, '00:00:00 local time'. Astronomers have deprecated the word
> 'midnight' for many years precisely to avoid this ambiguity.
Uh, I believe midnight is always the start of the day. I think
00:00:00 looks awkward.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajkumar Raghuwanshi | 2019-07-09 06:09:07 | Re: Postgres 11: Table Partitioning and Primary Keys |
| Previous Message | David G. Johnston | 2019-07-09 03:12:18 | Re: Postgres 11: Table Partitioning and Primary Keys |