Re: Ambiguous language in Table 8.13. Special Date/Time Inputs [EXT]

2019-07-11 Thread David Harper
> One really simple way to make it shorter is to say "00:00", leaving > out the seconds. That’s a good solution. It removes the long-standing ambiguity without looking too ugly. Best regards David Harper Wellcome Sanger Institute, Cambridge, England -- The Wellcome San

Re: Ambiguous language in Table 8.13. Special Date/Time Inputs [EXT]

2019-07-10 Thread David Harper
lled (as I did) to run a query such as select 'today'::timestamp,'yesterday'::timestamp,'tomorrow'::timestamp; on their PostgreSQL cluster to clear the ambiguity for themselves? Best regards David Harper Wellcome Sanger Institute, Cambridge, England -- The We

Re: Ambiguous language in Table 8.13. Special Date/Time Inputs [EXT]

2019-07-09 Thread David Harper
nd 2400 to designate the end of a given day (or date). = END QUOTE = Source: https://www.nist.gov/pml/time-and-frequency-division/times-day-faqs > I think 00:00:00 looks awkward. Perhaps, but in technical documentation, accuracy should have priority over aesthetics, surely? Dav