Re: Fix PL/Python metadata when there is no result

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Jean-Baptiste Quenot <jbq(at)caraldi(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fix PL/Python metadata when there is no result
Date: 2012-04-15 17:27:06
Message-ID: 1334510826.14312.1.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On fre, 2012-02-10 at 17:44 +0100, Jean-Baptiste Quenot wrote:
> Dear hackers,
>
> Thanks for the work on PLPython result metadata, it is very useful! I
> just came across a crash when trying to access this metadata on the
> result of an UPDATE, which obviously cannot return any tuple (unless
> you specify a RETURNING clause maybe?).
>
> Please find attached a patch that solves this issue. Instead of a PG
> crash, we get the following message:
>
> ERROR: plpy.Error: no result fetched

After much soul-searched about the API I have now committed your fix
that throws the exception. Thanks.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-04-15 19:13:23 Re: Last gasp
Previous Message Pavel Stehule 2012-04-15 16:48:53 Re: documentation bug - missing info about unpackaged control files for extension