From: | Holger Marzen <holger(at)marzen(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Solved: timestamp() broken in 7.2.4? |
Date: | 2003-06-27 05:30:33 |
Message-ID: | Pine.LNX.4.50.0306270727470.27794-100000@bluebell.marzen.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 26 Jun 2003, Stephan Szabo wrote:
> On Fri, 27 Jun 2003, Holger Marzen wrote:
>
> > In 7.1.3 I can use
> >
> > select timestamp(date '2001-01-01', time '00:00');
> >
> > but in 7.2.4 I get
> >
> > db1=# select timestamp(date '2001-01-01', time '00:00');
> > ERROR: parser: parse error at or near "date"
>
> To be closer to the standard, timestamp() became a reference to the
> datatype with a given precision (given in the parens). You can still get
> at the functions with "timestamp"(...), but I think you can also use
> date '2001-01-01' + time '00:00' as well.
Ah, I see. My condition
where interface = 'ppp0' and
age(current_timestamp, date + time) < '1 hour'
works now. I can simply add the columns date and time. Cool.
--
PGP/GPG Key-ID:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xB5A1AFE1
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Grant | 2003-06-27 06:00:50 | Re: How many fields in a table are too many |
Previous Message | Tom Lane | 2003-06-27 04:04:31 | Re: How many fields in a table are too many |