Re: Question about Postgresql time fields(possible bug)
| От | Harald Fuchs |
|---|---|
| Тема | Re: Question about Postgresql time fields(possible bug) |
| Дата | |
| Msg-id | 87psn0uis9.fsf@srv.protecting.net обсуждение исходный текст |
| Ответ на | Question about Postgresql time fields(possible bug) (Tony Caduto <tony_caduto@amsoftwaredesign.com>) |
| Ответы |
Re: Question about Postgresql time fields(possible bug)
|
| Список | pgsql-hackers |
In article <200601101551.k0AFpnK17299@candle.pha.pa.us>, 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 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'?
В списке pgsql-hackers по дате отправления: