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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
