| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PL/Python array support |
| Date: | 2009-11-04 16:06:38 |
| Message-ID: | 1257350798.12075.0.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On ons, 2009-11-04 at 09:44 -0500, Robert Haas wrote:
> On Wed, Nov 4, 2009 at 9:02 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > Here is a patch to support arrays in PL/Python as parameters and return
> > values. It converts an array parameter to a Python "list", and converts
> > a Python "sequence" return value back to an array.
>
> This is probably a stupid question, but why would you use different
> types for incoming and outgoing data flow?
A list is one particular kind of sequence.
See also
http://docs.python.org/reference/datamodel.html#the-standard-type-hierarchy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-04 16:27:08 | WIP: pushing parser hooks through SPI and plancache |
| Previous Message | Pavel Stehule | 2009-11-04 15:26:01 | actualised funcs typmod patch |