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: pgsql-bugs@postgresql.org, Jacek Jakubowski <jacek@wtal.de>, Malte Thoma <thoma@uni-muenster.de>
Date: 2001-11-02T15:20:46Z
Lists: pgsql-bugs
On Fri, Nov 02, 2001 at 11:49:03AM +0100, Christof Petig wrote:
> date ( some_timestamp_var ),  timestamp ( something ), timestamp
> (date_var, time_var ), interval('0sec')   are not longer possible.

Yes, there were some changes to this part of the parser.

> I don't know whether these constructs are legal in a 7.2 database, but
> we used them a lot in our code.

If they still work with the backend there's a bug in ecpg, but looking at
the sources suggests that it's working correctly.

> 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?

Michael

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