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

timestamp handling in postgres 7.1 behaves strange

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: timestamp handling in postgres 7.1 behaves strange
Date: 2001-08-08 22:44:20
Message-ID: 200108082244.f78MiKp65077@hub.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Martin Wrtele (martin(dot)wuertele(at)factline(dot)com) reports a bug with a severity of 1
The lower the number the more severe it is.

Short Description
timestamp handling in postgres 7.1 behaves strange

Long Description
version: 7.1release-4 of debian/woody

when comparing timestamps i always get
ERROR:  Bad timestamp external representation 'm'

Sample Code
this works:
select timestamp (content) from factversionelement where factid=100311 and elementname='newsdate';
       timestamp        
------------------------
 2010-01-02 16:00:00+01
(1 row)

this does not:
select factid from factversionelement where factid=100311 and elementname='newsdate' and timestamp (content) >= '2001-08-08';
ERROR:  Bad timestamp external representation 'm'

this also does not:
select factid from factversionelement where factid=100311 and elementname='newsdate' and timestamp (content) >= timestamp('2001-08-08');
ERROR:  Bad timestamp external representation 'm'


No file was uploaded with this report


Responses

pgsql-bugs by date

Next:From: Thomas LockhartDate: 2001-08-09 00:10:01
Subject: Re: timestamp handling in postgres 7.1 behaves strange
Previous:From: Thomas LockhartDate: 2001-08-08 01:32:59
Subject: Re: v7.0.2: can't use 'EXTRACT(EPOCH FROM'

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