Re: What does Time.MAX_VALUE actually represent?

Поиск
Список
Период
Сортировка
От Bear Giles
Тема Re: What does Time.MAX_VALUE actually represent?
Дата
Msg-id CALBNtw6Ftsxb=c+mYPd2sq=TZ8Q65XbWjOt0rf1FOmQMAhnsaw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: What does Time.MAX_VALUE actually represent?  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
Ответы Re: What does Time.MAX_VALUE actually represent?  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
Список pgsql-hackers
Дерево обсуждения
​You don't need to store 25:20 in the database though - your app can use a window that treats a day as "from 5 am today until 5 am tomorrow" and adds 24:00 to the times for tomorrow.​

Bear

On Sat, Dec 30, 2017 at 2:25 PM, Gavin Flower <GavinFlower@archidevsys.co.nz> wrote:
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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Remi Colinet
Дата:
Сообщение: [Patch] Make block and file size for WAL and relations defined atcluster creation
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: What does Time.MAX_VALUE actually represent?