Re: recent ECPG 7.1->7.2 incompatibility ( interval('0sec') = syntax error )

Michael Meskes <meskes@postgresql.org>

From: Michael Meskes <meskes@postgresql.org>
To: Christof Petig <christof@petig-baender.de>
Cc: Michael Meskes <meskes@postgresql.org>, pgsql-bugs@postgresql.org
Date: 2001-11-02T19:40:19Z
Lists: pgsql-bugs
On Fri, Nov 02, 2001 at 04:58:00PM +0100, Christof Petig wrote:
> > > cast ( some_timestamp_var as date), '0sec'::interval   and   "timestamp"
> > > (date_var, time_var)  still work but if this is just an oversight, I'd
> >
> > You mean it works with quotes but not without?
> 
> Yes:
> 
> exec sql select "interval"('0sec');  // accepted by ecpg
> exec sql select interval('0sec');     // not accepted by ecpg (yesterday's
> CVS)

Not really surprising I guess since "interval" is accepted as the string
>interval< while interval is regarded a token.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!