From: | Agent M <agentm(at)themactionfaction(dot)com> |
---|---|
To: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Timestamp vs timestamptz |
Date: | 2006-07-14 02:49:30 |
Message-ID: | 35c281a98e63653314971dc6a761744d@themactionfaction.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
But watch out! This is mentioned in the docs but it bit me when I used
timestamp with time zone so:
timestamp with time zone does not record the timezone you inserted it
with- it simply stores the GMT version and converts to whatever
timezone you like on demand. If the timezone is important data, you
will need an extra column for it. For example, flight arrival
information should probably include the timezone of the destination.
-M
On Jul 13, 2006, at 8:04 PM, David Fetter wrote:
> On Thu, Jul 13, 2006 at 04:35:20PM -0700, Antimon wrote:
>> Hi,
>> I'm working on a web project with pgsql, i did use mysql before and
>> stored epoch in database so i'm not familiar with these datatypes.
>>
>> What i wanna ask is, if i don't need to display timestamps in
>> different timezones,
>
> Not this week, but who knows about next week?
>
>> shall i use timestamptz anyway?
>
> Yes. Timestamptz is the one. :)
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬
AgentM
agentm(at)themactionfaction(dot)com
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick TJ McPhee | 2006-07-14 04:46:59 | Re: Physical block structure in PostgreSQL |
Previous Message | Tom Lane | 2006-07-14 02:30:34 | Re: Need help with quote escaping in exim for postgresql |