| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Christof Petig <christof(at)petig-baender(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Jacek Jakubowski <jacek(at)wtal(dot)de>, Malte Thoma <thoma(at)uni-muenster(dot)de> |
| Subject: | Re: recent ECPG 7.1->7.2 incompatibility ( interval('0sec') = syntax error ) |
| Date: | 2001-11-02 15:20:46 |
| Message-ID: | 20011102162046.C1532@feivel.fam-meskes.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)Fam-Meskes(dot)De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christof Petig | 2001-11-02 15:58:00 | Re: recent ECPG 7.1->7.2 incompatibility ( interval('0sec') = syntax |
| Previous Message | Christof Petig | 2001-11-02 10:49:03 | recent ECPG 7.1->7.2 incompatibility ( interval('0sec') = syntax error ) |