From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Doug McNaught <doug(at)mcnaught(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: plpgsql doesn't coerce boolean expressions to boolean |
Date: | 2003-09-08 16:57:06 |
Message-ID: | 3F5CB4E2.70506@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
Tom Lane wrote:
>Doug McNaught <doug(at)mcnaught(dot)org> writes:
>
>
>>I agree with another poster that deprecation in 7.4 and removal in
>>7.5 might make sense.
>>
>>
>
>How would we "deprecate" it exactly? Throw a NOTICE?
>
Good question. A NOTICE just might be ignored, breaking everything
"surprisingly" in 7.5.
To speak a bit more general, how about some sort of "deprecation
checker" setting, if set to true anything marked as deprecated will
throw an error, if false only a notice will be generated. This would
enable users to check their existing stuff for future compatibility
before it's broken in the next release.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Goudkov | 2003-09-08 16:58:20 | Temp tables and copy |
Previous Message | Doug McNaught | 2003-09-08 16:56:37 | Re: plpgsql doesn't coerce boolean expressions to boolean |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-09-08 18:27:10 | Re: plpgsql doesn't coerce boolean expressions to boolean |
Previous Message | Doug McNaught | 2003-09-08 16:56:37 | Re: plpgsql doesn't coerce boolean expressions to boolean |