| From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
|---|---|
| To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 'NOW' in UTC with no timezone |
| Date: | 2004-10-12 13:11:20 |
| Message-ID: | 35788438-1C50-11D9-A09B-000A95C88220@myrealbox.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Oct 12, 2004, at 9:43 PM, Karsten Hilbert wrote:
>>>> I'm trying to determine the best way of saying 'The current time in
>>>> UTC
>>>> with no time zone information'.
>>>
>>> Isn't that a contradiction in terms?
>>
>> Not if you're used to the Unix concept of storing "seconds since the
>> epoch".
>> In that model the quantity you're storing is entirely time zone
>> agnostic.
> But then one is storing an interval, not a point in time.
By that logic, all "times" are intervals. '2004-10-12 22:09' is 2004
years, 10 months, 12 days, 22 hours, 9 minutes since 0.
Michael Glaesemann
grzm myrealbox com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Fiche | 2004-10-12 13:46:05 | Confused with LABEL and LOOP |
| Previous Message | Jeff Boes | 2004-10-12 12:50:48 | Rule uses wrong value |