> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] 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 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.
pgAdmin III leaves all data checks in the hands of the database and
doesn't try to second guess what may or may not be valid - constraints
and regional settings might easily affect what is or isn't valid or how
client data is interpreted by the server.
Besides, 24:00:00 is an accepted way of indicating a leap second.
http://en.wikipedia.org/wiki/24-hour_notation
Regards, Dave
