Re: Question about Postgresql time fields(possible bug)

From: Harald Fuchs <hf0923x(at)protecting(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Question about Postgresql time fields(possible bug)
Date: 2006-01-10 16:52:54
Message-ID: 87psn0uis9.fsf@srv.protecting.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

In article <200601101551(dot)k0AFpnK17299(at)candle(dot)pha(dot)pa(dot)us>,
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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 also incorrect,
>> PG Lightning Admin catches it as a invalid time, but shouldn't there be
>> some validation of times and dates at the server level?
>>
>> There are people who are using PG Admin III and they don't even know
>> they have bogus dates and times in their databases.

> 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'?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-01-10 17:14:58 Re: Question about Postgresql time fields(possible bug)
Previous Message Tom Lane 2006-01-10 16:26:50 Re: current_setting returns 'unset'