Skip site navigation (1) Skip section navigation (2)

[SQL/BUGS] (possible) inconsistent behaviour of timestamp?

From: "Rison, Stuart" <srison(at)rvc(dot)ac(dot)uk>
To: "'pgsql-sql(at)postgresql(dot)org'" <pgsql-sql(at)postgresql(dot)org>,"'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: [SQL/BUGS] (possible) inconsistent behaviour of timestamp?
Date: 2002-11-26 13:54:03
Message-ID: 6BD8CE460CC6EE40B83DDFCED609F84BE140D8@cmnt4008.rvc.ac.uk (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-sql
Here's an "interesting" timestamp related postgreSQL quirk:

testdb2=# select "timestamp"('now');
         timestamp
----------------------------
 2002-11-26 13:47:12.454157
(1 row)

testdb2=# select 'now'::timestamp;
         timestamptz
------------------------------
 2002-11-26 13:47:34.88358+00
(1 row)

testdb2=# select timestamp 'now';
          timestamptz
-------------------------------
 2002-11-26 13:47:47.701731+00
(1 row)

The first SELECT returns a 'timestamp', but the next two return a
'timestamptz' (presumably with timezone); is this inconsitent behaviour?

Cheers,

Stuart.
Royal Veterinary College
London, UK

Responses

pgsql-bugs by date

Next:From: Rod TaylorDate: 2002-11-26 14:43:23
Subject: Re: vacumm error
Previous:From: pgsql-bugsDate: 2002-11-26 11:54:41
Subject: Bug #823: upper() does not handle , and correctly.

pgsql-sql by date

Next:From: Rison, StuartDate: 2002-11-26 13:54:20
Subject: Two TIMESTAMPs in one pl/sql function
Previous:From: Zuev DmitryDate: 2002-11-26 13:14:07
Subject: help on sql query

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group