Re: definative way to place secs from epoc into timestamp

From: Ken Johanson <pg-user(at)kensystem(dot)com>
To: andrew(at)supernews(dot)com
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: definative way to place secs from epoc into timestamp
Date: 2005-03-04 15:20:24
Message-ID: 42287CB8.7040600@kensystem.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

>>and the fact that I want the same value from the data base that I put
>>into it.
>
>
> "same" in which sense? The same absolute point in time? Or the same point
> on a calendar? Obviously if the timezone doesn't change, then the two are
> equivalent; but which one is your application actually looking for? (If
> your app is using Unix epoch times, then it's looking only at the absolute
> time and not the calendar time...)
>

Unix time stamps, short (int) or long res, are always supposed to GMT
based, as far as I know - I never seen anything different, except maybe
in homebrew software. So it should be both calendar and P.I.T. And you
wouldn't need the TZ storage if the date-number and number-> translation
itself takes the TZ arg so that it can localize the Human String for you.

Ken

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Ken Johanson 2005-03-04 15:29:09 Re: definative way to place secs from epoc into timestamp
Previous Message Tom Lane 2005-03-04 15:14:14 Re: definative way to place secs from epoc into timestamp