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

From Tom Lane
Subject Re: Fix PL/Python metadata when there is no result
Date
Msg-id 20477.1331158442@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fix PL/Python metadata when there is no result  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Fix PL/Python metadata when there is no result  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On ons, 2012-03-07 at 16:49 -0500, Tom Lane wrote:
>> Still, it seems rather arbitrary to say that the row count property is
>> the thing to test for that purpose and no other is.  Why not return None
>> for any property that's not sensible?

> Hmm, above you said you were in favor of throwing an error rather than
> returning None?

I said it was a reasonable alternative, not that it was the only one
we should consider.  The behavior of .nrows() might be accidental,
but perhaps it is a preferable model to adopt.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Fix PL/Python metadata when there is no result
Next
From: Robert Haas
Date:
Subject: Re: patch for a locale-specific bug in regression tests (REL9_1_STABLE)