On Thu, Nov 24, 2011 at 12:30 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> There are small issue in PL/pgSQL and custom exceptions. Custom
> exception doesn't set a CONTEXT field. I propose change this behave
> for WARNING or EXCEPTION level. The goal is same behave for custom
> exception and builtin exception and it can help to identify a RAISE
> statement that is responsible to exception.
That seems completely arbitrary. I think we discussed before
providing an option to allow the user to control this, which seems
better than implementing some hardcoded rule that may or may not be
what a given user wants.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
