Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Timestamp with time zone: why not?
- 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: Thu, 24 May 2007 06:05:17 -0700 (PDT)
- Message-id: <Pine(dot)LNX(dot)4(dot)64(dot)0705240558020(dot)22282(at)salmo(dot)appl-ecosys(dot)com>
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
- References:
- Timestamp with time zone: why not?
- From: km
- Timestamp with time zone: why not?
- Prev by Date: Re: why postgresql over other RDBMS
- Next by Date: Re: the future of pljava development
- Previous by thread: Re: Timestamp with time zone: why not?
- Next by thread: Re: Timestamp with time zone: why not?
- Indexes: