| From: | Christof Petig <christof(at)petig-baender(dot)de> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Cc: | Jacek Jakubowski <jacek(at)wtal(dot)de>, Malte Thoma <thoma(at)uni-muenster(dot)de>, Michael Meskes <meskes(at)postgresql(dot)org> |
| Subject: | recent ECPG 7.1->7.2 incompatibility ( interval('0sec') = syntax error ) |
| Date: | 2001-11-02 10:49:03 |
| Message-ID: | 3BE27A1F.B762253F@petig-baender.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hello,
while switching to the 7.2 ecpg on a 7.1 database for it's new features,
we recognized several incompatibilities:
date ( some_timestamp_var ), timestamp ( something ), timestamp
(date_var, time_var ), interval('0sec') are not longer possible.
I don't know whether these constructs are legal in a 7.2 database, but
we used them a lot in our code.
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
recommend to fix it.
Yours
Christof
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2001-11-02 15:20:46 | Re: recent ECPG 7.1->7.2 incompatibility ( interval('0sec') = syntax error ) |
| Previous Message | Tom Lane | 2001-11-01 18:45:05 | Re: Union View Optimization |