Re: [BUGS] BUG #5272: PL/Python SELECT: return composite fields as dict, not str

2010-03-29 Thread Peter Eisentraut
On sön, 2010-01-31 at 13:20 +0100, Steve White wrote: Robert suggested that I start some documentation about limitations of PL/Python. Find attached. I think it would also be good to explain the meaning of trusted regarding PL/Python, and how it might impact the user. There is already some

Re: [BUGS] BUG #5272: PL/Python SELECT: return composite fields as dict, not str

2010-01-31 Thread Steve White
Hi all, Robert suggested that I start some documentation about limitations of PL/Python. Find attached. I think it would also be good to explain the meaning of trusted regarding PL/Python, and how it might impact the user. There is already some commented-out doc, and also something in the

Re: [BUGS] BUG #5272: PL/Python SELECT: return composite fields as dict, not str

2010-01-11 Thread Robert Haas
On Mon, Jan 11, 2010 at 11:41 AM, Steve White swh...@aip.de wrote: I see nothing in the documentation about this        http://www.postgresql.org/docs/8.4/static/plpython.html It only talks about passing composite types into and out of functions. This is an unpleasant discovery for those