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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-11-26 14:43:23 | Re: vacumm error |
Previous Message | pgsql-bugs | 2002-11-26 11:54:41 | Bug #823: upper() does not handle , and correctly. |
From | Date | Subject | |
---|---|---|---|
Next Message | Rison, Stuart | 2002-11-26 13:54:20 | Two TIMESTAMPs in one pl/sql function |
Previous Message | Zuev Dmitry | 2002-11-26 13:14:07 | help on sql query |