From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | "David Fetter" <david(at)fetter(dot)org>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/Perl: spi_prepare() and RETURNING |
Date: | 2006-08-27 23:49:44 |
Message-ID: | 13299.1156722584@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> On 8/24/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
> 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.
I've applied a patch along these lines. David's plperl example now does
what (I think) he expected. Does anyone want to extend the plperl,
pltcl, plpython regression tests to check behavior with INSERT RETURNING
etc?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-08-28 01:22:18 | Re: Adding fulldisjunctions to the contrib |
Previous Message | Michael Glaesemann | 2006-08-27 23:31:06 | Interval month, week -> day |