Re: plpgsql doesn't coerce boolean expressions to boolean

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql doesn't coerce boolean expressions to boolean
Date: 2003-09-08 21:31:33
Message-ID: 3F5CF535.6070202@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>
>>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.
>
>
>
I thought I had seen discussions along the lines of "we'll give them one
cycle to fix it and then they are shot".

It does seem very late in this cycle to make such changes.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-09-08 21:33:02 Re: undefine currval()
Previous Message Tom Lane 2003-09-08 21:29:10 Re: pgsql in shared lib

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2003-09-08 21:33:02 Re: undefine currval()
Previous Message Chris Gamache 2003-09-08 21:12:54 undefine currval()