Re: Fix PL/Python metadata when there is no result - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Fix PL/Python metadata when there is no result
Date
Msg-id 1331153242.12416.5.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Fix PL/Python metadata when there is no result  (Jean-Baptiste Quenot <jbq@caraldi.com>)
Responses Re: Fix PL/Python metadata when there is no result  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On lör, 2012-02-25 at 18:03 +0100, Jean-Baptiste Quenot wrote:
> IMO raising an error is much better because:
> 
> 1) It is not a valid usecase to retrieve result metadata when no rows
> are expected to be returned

Which led me to think, how are you actually expected to know when no
rows are expected to be returned, in PL/Python?  You can look at
result.status(), which returns a numeric SPI status, but that seems
fragile.  I notice that result.nrows() returns None when no rows are
returned.  Is that good enough?  In that case, we should document that
and then make the new functions throw exceptions like you suggest.




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: WARNING: concurrent insert in progress within table "resource"
Next
From: Larry Rosenman
Date:
Subject: Re: CLUSTER VERBOSE (9.1.3)