From: | Casey Allen Shobe <cshobe(at)secureworks(dot)net> |
---|---|
To: | Rod Taylor <rbt(at)rbt(dot)ca> |
Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Postgres storing time in strange manner |
Date: | 2002-09-15 14:16:23 |
Message-ID: | 200209151016.23932.cshobe@secureworks.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-novice |
On Sunday 15 September 2002 10:11 am, Rod Taylor wrote:
> On Sun, 2002-09-15 at 03:57, Casey Allen Shobe wrote:
> > I don't have a clue why it's doing this - has anyone else seen this sort
> > of behavior, or know why it might be doing it? It shows times wrong, for
> > instance, it shows 00:04:60 where it should show 00:05:00. See below:
>
> There are actually 61 seconds in some minutes. In order to accommodate
> leap seconds, PostgreSQL allows this to happen -- similarly to how it
> will also allow 366 days in some years.
How then, am I supposed to explain to a web interface user that when they just
entered 5:00:00, it's going to sometimes show up to 4:59:60?
I'm entering an exact timestamp, that being 5:00:00. Regardless of how many
seconds you claim were in the former minute, it should not subtract a second
from my entry, because 5:00:00 by your definition would mean 4:59 and 61
seconds.
--
Casey Allen Shobe / Network Security Analyst & PHP Developer
SecureWorks, Inc. / 404.327.6339 x169 / Fax: 404.728.0144
cshobe(at)secureworks(dot)net / http://www.secureworks.net
Content is my own and does not necessarily represent my company.
Dance like nobody's watching.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-15 14:32:35 | Re: Postgres storing time in strange manner |
Previous Message | botik32 | 2002-09-15 14:11:14 | Memory leak in client application |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-15 14:32:35 | Re: Postgres storing time in strange manner |
Previous Message | Rod Taylor | 2002-09-15 14:11:04 | Re: Postgres storing time in strange manner |