"Rison, Stuart" <srison(at)rvc(dot)ac(dot)uk> writes:
> The first SELECT returns a 'timestamp', but the next two return a
> 'timestamptz' (presumably with timezone); is this inconsitent behaviour?
Yes. It's a transitional behavior in 7.2: timestamp without any quotes
is translated by the parser to timestamptz (ie, timestamp with time
zone). Quotes suppress the renaming, however.
We did that deliberately for one release to ease updating, because PG's
old "datetime" datatype corresponds to timestamptz, not timestamp-without-
time-zone. As of 7.3 that renaming doesn't happen any more, and
undecorated timestamp means timestamp without time zone, per spec.
Confused yet? I'm not sure that this update plan was really a great
idea, but we agreed to it a release or two back, and we're sticking to
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2002-11-27 02:20:24|
|Subject: Re: version for sun cobalt qube 3 |
|Previous:||From: Tom Lane||Date: 2002-11-27 02:02:11|
|Subject: Re: Bug #823: upper() does not handle , and correctly. |
pgsql-sql by date
|Next:||From: Achilleus Mantzios||Date: 2002-11-27 08:00:37|
|Subject: Re: SQL -select count-|
|Previous:||From: Peter Eisentraut||Date: 2002-11-26 23:52:26|
|Subject: Re: copy from command - quotes and header lines|