From: Tom Lane <tgl@sss.pgh.pa.us>
To: Euler Taveira <euler@eulerto.com>
Cc: arturocuya099@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Re: About the return states of SPI_execute for plpy.execute().status()
Date: Wed, 17 Feb 2021 14:58:47 -0500
Message-ID: <2743963.1613591927@sss.pgh.pa.us> (raw)
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>
"Euler Taveira" <euler@eulerto.com> writes:
> It is referring to the SPI_execute() return values [1] whose mapped integers
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, euler@eulerto.com, arturocuya099@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Re: About the return states of SPI_execute for plpy.execute().status()
In-Reply-To: <2743963.1613591927@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox