Re: Bug in plpython's Python Generators - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Bug in plpython's Python Generators
Date
Msg-id 1287686694-sup-8959@alvh.no-ip.org
Whole thread Raw
In response to Re: Bug in plpython's Python Generators  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Bug in plpython's Python Generators
List pgsql-hackers
Excerpts from Alvaro Herrera's message of jue oct 21 15:32:53 -0300 2010:
> Excerpts from Jean-Baptiste Quenot's message of jue oct 21 09:20:16 -0300 2010:
>
> > I get this error when calling the function:
> >
> > test=# select foobar();
> > ERROR:  error fetching next item from iterator
>
> I can reproduce this here.  The first bug to solve is, I think, getting
> a more meaningful error report.

Something like this.  Somebody that really knows their way around Python
has to clean this up.

alvherre=# select * from foobar();
ERROR:  error extrayendo el próximo elemento del iterador
CONTEXTO:  falló SPI_execute: SPI_ERROR_UNCONNECTED
función PL/Python «foobar»

I think all error cases in plpython need some improvement so that they
show the error message from Python.  Right now they are ignored.

... and presumably somebody can fix the real bug that Jean-Baptiste hit,
too.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Per-column collation, work in progress
Next
From: Cédric Villemain
Date:
Subject: Re: Exposing an installation's default value of unix_socket_directory