Re: Comment on timezone and interval types
От | Stuart Bishop |
---|---|
Тема | Re: Comment on timezone and interval types |
Дата | |
Msg-id | 418B3BF1.4000200@stuartbishop.net обсуждение исходный текст |
Ответ на | Re: Comment on timezone and interval types (Bruno Wolff III <bruno@wolff.to>) |
Ответы |
Re: Comment on timezone and interval types
Re: Comment on timezone and interval types |
Список | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruno Wolff III wrote: | On Fri, Oct 29, 2004 at 11:14:31 -0600, | Guy Fraser <guy@incentre.net> wrote: | |>1 day should always be calculated as 24 hours, just as an hour |>is calculated as 60 minutes... | | | If you want 24 hours you can use 24 hours. Days are not constant length, | just like months aren't constant length. Days *are* of constant length - check your nearest dictionary, which will define it as 24 hours or the period of rotation of the earth. If people see 'day', they think '24 hours' because that is the definition they have been using since preschool. This breeds sleeping bugs that nobody notices until the DST transition kicks in and events happen an hour late or not at all. What you are talking about is useful, but should be called calendar_day or something that makes it obvious that it isn't using the traditional definition. People are used to months being ambiguous so it is less likely to cause upsets, although it still bites people because their toolkits definition of 'month' does not match their business rules of 'month' (which might be 30 days, 31 days, 4 weeks, calendar month rounded down). - -- Stuart Bishop <stuart@stuartbishop.net> http://www.stuartbishop.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBizvxAfqZj7rGN0oRAqLAAJ9sNmXB/yv/P6saytH4qrPQ9xdwEACfX8I9 krauCgYalcWsW+7qiPymoYo= =pMyc -----END PGP SIGNATURE-----
В списке pgsql-general по дате отправления: