From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Timestamp with time zone: why not? |
Date: | 2007-05-24 13:05:17 |
Message-ID: | Pine.LNX.4.64.0705240558020.22282@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 23 May 2007, 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'?
If the application's users are in different time zones, or accurate time
intervals are important, then time zones should be part of the stored data.
If this is not an issue, and will not be an issue, it does not matter.
However, using 'WITH TIME ZONE' in the DDL means that if the situation
changes you are covered.
Rich
--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc. | Accelerator(TM)
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
From | Date | Subject | |
---|---|---|---|
Next Message | Marek Lewczuk | 2007-05-24 13:07:39 | Re: the future of pljava development |
Previous Message | Jon Clements | 2007-05-24 12:32:25 | Limiting number of rows returned at a time in select query |