From: Robert Haas <robertmhaas@gmail.com>
To: Steve White <swhite@aip.de>
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #5272: PL/Python SELECT: return composite fields as dict, not str
Date: Mon, 11 Jan 2010 21:31:57 -0500
Message-ID: <603c8f071001111831j5b05b57cs108d2792c390e26@mail.gmail.com> (raw)
In-Reply-To: <201001111641.o0BGf7cw063967@wwwmaster.postgresql.org>
References: <201001111641.o0BGf7cw063967@wwwmaster.postgresql.org>
On Mon, Jan 11, 2010 at 11:41 AM, Steve White <swhite@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 working to a deadline. Perhaps a
> "limitations" section for the doc would be in order. (You could also list
> the limitations of PL/Python regarding returning RECORD types.)
Maybe you could suggest some text, perhaps in the form of a context
diff against the current sgml files?
> But the best thing to do would be to fix it.
Doubtless. Of course it will depend on whether anyone finds enough
round tuits. Peter Eisentraut made some improvements to PL/python
array handling which will be in the next major release, but I am not
aware of anyone working on record types. This is an all-volunteer
effort, so people tend to scratch their own itches.
> For backward compatibility, you might implement a switch that turns on the
> hierarchical interpretation of fields, and leave the current behaviour as
> the default.
I suspect we wouldn't bother with that.
...Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: robertmhaas@gmail.com, swhite@aip.de
Subject: Re: BUG #5272: PL/Python SELECT: return composite fields as dict, not str
In-Reply-To: <603c8f071001111831j5b05b57cs108d2792c390e26@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox