| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
| Subject: | Re: timestamp with time zone a la sql99 |
| Date: | 2004-10-25 20:32:37 |
| Message-ID: | 23329.1098736357@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> As long as we're willing to live with the understanding that +1day 1 hour may
> produce a slightly different result than + 25 hours, I don't see the problem.
Right, which is exactly why we can't accept the spec's restriction that
the hour field be limited to 0-23. People may legitimately want to add
48 hours to a timestamp, and *not* have that mean the same as adding
"2 days". Besides, we would have a backwards-compatibility problem if
we tried to forbid it, since as you note we've always accepted such input.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-10-25 20:54:53 | Lamar stepping down |
| Previous Message | Dennis Bjorklund | 2004-10-25 20:22:29 | Re: timestamp with time zone a la sql99 |