From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Timestamp with time zone: why not? |
Date: | 2007-05-24 05:10:32 |
Message-ID: | 46551E48.6080206@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/23/07 18:54, km(at)acrasis(dot)net wrote:
> Would I be right in thinking that, in general, a column to hold
> timestamp values is best created with type 'TIMESTAMP WITH TIME ZONE'
> and not 'TIMESTAMP' nor 'TIMESTAMP WITHOUT TIME ZONE'?
>
> To put it another way, for what reasons might the 'TIMESTAMP' type be
> preferred to 'TIMESTAMP WITH TIME ZONE'?
Importing data from a legacy system that doesn't "do" timezones.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGVR5HS9HxQb37XmcRAilwAJ9JSQEWDNdRUePIP+wXlHBEN0sG8gCg50K5
ccYj7+WkwdL7CkfoOgDEHDs=
=h+pn
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-24 05:11:52 | Re: Vacuum DB in Postgres Vs similar concept in other RDBMS |
Previous Message | Ron Johnson | 2007-05-24 05:05:16 | Re: Integrity on large sites |