From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Euler Taveira" <euler@eulerto.com>
cc: arturocuya099@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re:
 =?UTF-8?Q?Re:_About_the_return_states_of_SPI=5Fexecute_for_plpy.execute(?=
 =?UTF-8?Q?).status()?=
In-reply-to: <a3e40711-51a2-4421-834f-d7c072a057ee@www.fastmail.com>
References: <161340270933.3462.11448419214943107350@wrigleys.postgresql.org>
 <a3e40711-51a2-4421-834f-d7c072a057ee@www.fastmail.com>
Comments: In-reply-to "Euler Taveira" <euler@eulerto.com>
	message dated "Wed, 17 Feb 2021 16:43:58 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2743962.1613591927.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Feb 2021 14:58:47 -0500
Message-ID: <2743963.1613591927@sss.pgh.pa.us>
Precedence: bulk

"Euler Taveira" <euler@eulerto.com> writes:
> It is referring to the SPI_execute() return values [1] whose mapped inte=
gers       =

> are available in [2]. 11 refers to INSERT ... RETURNING. Maybe PL/Python=
 should
> expose these SPI constants too (if it doesn't).

I wouldn't be in too much of a hurry to do that, because there's been
repeated discussion of removing (or at least obsoleting) most of those
codes in favor of throwing regular errors for the cases that represent
error conditions.  Better to wait to change plpython until after that
dust settles.

			regards, tom lane