Re: What does Time.MAX_VALUE actually represent?

2018-01-01 Thread Gavin Flower
On 01/02/2018 01:26 AM, Tels wrote: Moin, On Sat, December 30, 2017 4:25 pm, Gavin Flower 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

Re: What does Time.MAX_VALUE actually represent?

2018-01-01 Thread Tels
Moin, On Sun, December 31, 2017 12:50 pm, Tom Lane wrote: > Peter Eisentraut writes: >> select timestamp '2017-12-30 24:00:00'; >> returns >> 2017-12-31 00:00:00 >> which makes some sense. > >> I don't know why we accept that and not '24:00:01' and beyond, but

Re: What does Time.MAX_VALUE actually represent?

2018-01-01 Thread Tels
Moin, On Sat, December 30, 2017 4:25 pm, Gavin Flower 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

Re: What does Time.MAX_VALUE actually represent?

2017-12-31 Thread Gavin Flower
Hi Bear, Please don't top post! On 01/01/2018 06:17 AM, Bear Giles wrote: ​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

Re: What does Time.MAX_VALUE actually represent?

2017-12-31 Thread Tom Lane
Peter Eisentraut writes: > select timestamp '2017-12-30 24:00:00'; > returns > 2017-12-31 00:00:00 > which makes some sense. > I don't know why we accept that and not '24:00:01' and beyond, but it's > probably historical. We also accept regression=# select

Re: What does Time.MAX_VALUE actually represent?

2017-12-31 Thread Peter Eisentraut
On 12/30/17 09:07, 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 select timestamp '2017-12-30 24:00:00'; returns 2017-12-31 00:00:00 which makes some sense. I don't know

Re: What does Time.MAX_VALUE actually represent?

2017-12-31 Thread Bear Giles
​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 wrote: > On 12/31/2017

Re: What does Time.MAX_VALUE actually represent?

2017-12-30 Thread Gavin Flower
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

What does Time.MAX_VALUE actually represent?

2017-12-30 Thread Dave Cramer
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