| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Casey Allen Shobe <cshobe(at)secureworks(dot)net> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Postgres storing time in strange manner |
| Date: | 2002-09-15 14:49:22 |
| Message-ID: | 1032101363.19130.26.camel@jester |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-novice |
> 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?
Oh, I see. I thought you were doing some interval math on it. Yes,
your right, it should be taken as being 5:00:00.
> 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.
Either way, I've been unable to reproduce it with either 7.2 or 7.3 --
nor do I see any notes about that feature having been removed or carried
over to current releases -- no regression tests for it in 7.3.
Could you provide a complete test case, or confirm that it does what you
expect in 7.3?
7.2.2:
iqdb=# select '0001-01-01 4:59:60'::timestamptz;
ERROR: Bad timestamp external representation '0001-01-01 4:59:60'
--
Rod Taylor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-09-15 14:51:34 | Re: Postgres storing time in strange manner |
| Previous Message | Tom Lane | 2002-09-15 14:32:35 | Re: Postgres storing time in strange manner |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-09-15 14:51:34 | Re: Postgres storing time in strange manner |
| Previous Message | Tom Lane | 2002-09-15 14:32:35 | Re: Postgres storing time in strange manner |