[EMAIL PROTECTED] writes:
> 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 f
> when comparing timestamps i always get
> ERROR: Bad timestamp external representation 'm'
> this works:
> select timestamp (content) from factversionelement where factid=100311 and
>elementname='newsdate';
>
> 2010-01-02 16:00:00+01
> this does not:
> select factid fr
Martin Würtele ([EMAIL PROTECTED]) 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 timest
