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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Steve White <swhite(at)aip(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5272: PL/Python SELECT: return composite fields as dict, not str
Date: 2010-03-29 21:36:42
Message-ID: 1269898602.6144.15.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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
> commented-out doc, and also something in the PL/Perl section.
> Specifically, a user might want to know if it is actually dangerous to
> use PL/Python, etc. If it is dangerous, how, and for whom? Where should
> one be careful?

I have added some documentation for both of these issues along the lines
suggested by you.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andy Balholm 2010-03-29 23:37:00 dividing money by money
Previous Message Stefan Kaltenbrunner 2010-03-29 11:16:11 Re: Known Issues Page