Re: PL/Perl: spi_prepare() and RETURNING - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: PL/Perl: spi_prepare() and RETURNING
Date
Msg-id 36e682920608241222s40228dcdsdbcec91220f4f504@mail.gmail.com
Whole thread Raw
In response to Re: PL/Perl: spi_prepare() and RETURNING  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PL/Perl: spi_prepare() and RETURNING
List pgsql-hackers
On 8/24/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This reminds me of a consideration I had been intending to bring up on
> the mailing lists: what exactly do we want to do with the SPI API for
> RETURNING queries?  The current behavior is that it still returns
> SPI_OK_INSERT and so on, but also creates a SPI_tuptable.  Is this
> what we want?  Perhaps we should invent additional return codes
> SPI_OK_INSERT_RETURNING etc.

I like adding RETURNING-specific return codes.

> Another issue I noted in that same area is that spi.c does not set
> SPI_processed for a utility statement, even if the utility statement
> returns tuples.  Is this a bug, or should we leave it alone?

I think it's a bug.

-- 
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation            | fax: 732.331.1301
33 Wood Ave S, 2nd Floor            | jharris@enterprisedb.com
Iselin, New Jersey 08830            | http://www.enterprisedb.com/


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: PL/Perl: spi_prepare() and RETURNING
Next
From: Tom Lane
Date:
Subject: Re: Tricky bugs in concurrent index build