From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Timezone information |
Date: | 2014-02-20 12:59:53 |
Message-ID: | CALSLE1O5L=tATwhvsC+oNCK4yAY0jDgVFjHx4eSuh8P3VbAx5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Feb 20, 2014 at 4:31 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>wrote:
> It depends on how you are declaring the timestamp field. If you do not use
> with time zone then the input value is open to interpretation and is not
> 'anchored' to a point in time.
>
> Example
>
> My time zone is currently PST.
> test=> create table timestamp_test(id int, ts timestamp, ts_z timestamp
> with time zone);
> CREATE TABLE
> test=> insert into timestamp_test values (1, now(), now());
> INSERT 0 1
> .....
> If you know what time zone the value was inserted under you can get it
> back.
> .
> .
> That assumes a lot, so the best thing is to use timestamp with time zone.
Thanks for trying this out on your setup. However looks like my requirement
is different here.
Regards...
From | Date | Subject | |
---|---|---|---|
Next Message | Dev Kumkar | 2014-02-20 13:04:31 | Re: UTF-8 collation on Windows? |
Previous Message | Dev Kumkar | 2014-02-20 12:52:52 | Re: Timezone information |