| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql doesn't coerce boolean expressions to boolean |
| Date: | 2003-09-08 20:28:38 |
| Message-ID: | 453.1063052918@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> How would we "deprecate" it exactly? Throw a NOTICE?
>>
> Release notes, I guess. A NOTICE would be fine as long as it didn't
> result in a flood of them. If that happened once at parse time that
> should be fine, I think.
It would be relatively difficult to do that; given the way plpgsql is
structured, a runtime message would be a lot easier.
> What's the practice in deprecating other "features"?
We generally don't ;-). Certainly 7.4 contains bigger incompatible
changes than this one, and so have most of our prior releases.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-08 20:29:56 | Re: ISO 8601 "Time Intervals" of the "format with time-unit |
| Previous Message | Bruce Momjian | 2003-09-08 20:27:16 | Re: ISO 8601 "Time Intervals" of the "format with time-unit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Gamache | 2003-09-08 21:12:54 | undefine currval() |
| Previous Message | Andrew Dunstan | 2003-09-08 18:27:10 | Re: plpgsql doesn't coerce boolean expressions to boolean |