Re: What does Time.MAX_VALUE actually represent?

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: What does Time.MAX_VALUE actually represent?
Date: 2017-12-30 21:25:40
Message-ID: 660adac2-35b2-f0eb-d6f6-f40ddcfa272b@archidevsys.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/31/2017 03:07 AM, Dave Cramer wrote:
> We are having a discussion on the jdbc project about dealing with
> 24:00:00.
>
> https://github.com/pgjdbc/pgjdbc/pull/992#issuecomment-354507612
>
> Dave Cramer

In Dublin (I was there 2001 to 2004), Time tables show buses just after
midnight, such as 1:20am as running at the time 2520 - so there are
visible close to the end of the day.  If you are looking for buses
around midnight this is very user friendly - better than looking at the
other end of the time table for 0120.

I think logically that 24:00:00 is exactly one day later than 00:00:00 -
but I see from following the URL, that there are other complications...

Cheers,
Gavin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-12-30 21:46:41 Better testing coverage and unified coding for plpgsql loops
Previous Message Joe Conway 2017-12-30 21:04:52 Re: [HACKERS] Re: [HACKERS] generated columns