Re: BUG #16048: SQLSTATE 22P05 is not captured in exception clause - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16048: SQLSTATE 22P05 is not captured in exception clause
Date
Msg-id 16177.1570803560@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16048: SQLSTATE 22P05 is not captured in exception clause  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
>         I have a database using LATIN1 (and I can't change it), so, when the
> user informar a invalid character it is not captured in exception clause.
> See a short sample:

> DO $$
> DECLARE 
>    v varchar;
> BEGIN
>    v := 'ABCŸ';
> EXCEPTION
> WHEN others THEN
> RAISE INFO 'Error State: %', SQLSTATE;
> END$$;

Sorry, that's not a bug, and you're going to have to find some other
way to deal with the issue.  This error will be thrown while trying to
convert the incoming query string to the database encoding, long before
anything in the server would be able to recognize that this even is a
DO command, let alone is one containing an exception clause.

Exception clauses don't work for syntax errors either, for largely
similar reasons.

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16049: log_line_prefix=%a and log_connections - application_name missing
Next
From: Tom Lane
Date:
Subject: Re: BUG #16049: log_line_prefix=%a and log_connections - application_name missing