Hi,
I just noticed today that Postgresql accepts a value of 24:00:00, this
is for sure not correct as there is no such thing as 24:00:00
PG Admin III will display this value just fine which is also incorrect,
PG Lightning Admin catches it as a invalid time, but shouldn't there be
some
Tony Caduto wrote:
Hi,
I just noticed today that Postgresql accepts a value of 24:00:00, this
is for sure not correct as there is no such thing as 24:00:00
PG Admin III will display this value just fine which is also incorrect,
PG Lightning Admin catches it as a invalid time, but
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony Caduto
Sent: 10 January 2006 15:38
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] Question about Postgresql time fields(possible bug)
Hi,
I just noticed today that Postgresql accepts
In article [EMAIL PROTECTED],
Bruce Momjian pgman@candle.pha.pa.us writes:
Tony Caduto wrote:
Hi,
I just noticed today that Postgresql accepts a value of 24:00:00, this
is for sure not correct as there is no such thing as 24:00:00
PG Admin III will display this value just fine which is
Harald Fuchs [EMAIL PROTECTED] writes:
Bruce Momjian pgman@candle.pha.pa.us writes:
A leap second will show as 24:00:00. It is a valid time.
Shouldn't such a leap second be represented as '... 23:59:60'?
People who didn't like 24:00:00 would complain about that, too ;-)
Actually, my
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harald Fuchs
Sent: 10 January 2006 16:53
To: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Question about Postgresql time
fields(possible bug)
In article [EMAIL PROTECTED],
Bruce Momjian
In article [EMAIL PROTECTED],
Tom Lane [EMAIL PROTECTED] writes:
Harald Fuchs [EMAIL PROTECTED] writes:
Bruce Momjian pgman@candle.pha.pa.us writes:
A leap second will show as 24:00:00. It is a valid time.
Shouldn't such a leap second be represented as '... 23:59:60'?
People who didn't
On 10/1/06 18:00, Tony Caduto [EMAIL PROTECTED] wrote:
Dave Page wrote:
On looking further it appears to me that 24:00:00 is not a leap second
(which definitely can be 23:50:60), but just another way of expressing
midnight.
From: http://www.cl.cam.ac.uk/~mgk25/iso-time.html
Tony, Dave,
That's not really the point. The ISO 8601 standard allows midnight to be
expressed as 00:00:00 or 24:00:00 to enable you to tell which midnight
is being referred to (ie. The beginning or the end of the day).
IIRC, the reason for supporting 24:00:00 is that some popular client
Dave Page dpage@vale-housing.co.uk writes:
That's not really the point. The ISO 8601 standard allows midnight to be
expressed as 00:00:00 or 24:00:00 to enable you to tell which midnight is
being referred to (ie. The beginning or the end of the day).
There are other reasons for allowing it
That's not really the point. The ISO 8601 standard allows midnight to be
expressed as 00:00:00 or 24:00:00 to enable you to tell which midnight is
being referred to (ie. The beginning or the end of the day).
PostgreSQL allows you to make use of that part of the standard, and as admin
tool
11 matches
Mail list logo
