| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>,Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>,Alexey Grishchenko <programmerag(at)gmail(dot)com>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/Python adding support for multi-dimensional arrays |
| Date: | 2016-10-14 16:24:16 |
| Message-ID: | A86513E6-B34D-43C8-A4B4-B700C7A9DA6F@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14 October 2016 19:18:01 EEST, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> wrote:
>On 10/14/16 3:53 AM, Heikki Linnakangas wrote:
>> Composite types in arrays must now be returned as
>> Python tuples, not lists, to resolve the ambiguity. I.e. "[(col1,
>col2),
>> (col1, col2)]".
>
>Shouldn't dicts be allowed as well?
Ah yes, dicts are also allowed, as before. And strings. The only change is that a list is interpreted as an array dimension, instead of a composite type.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-10-14 16:43:47 | Re: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits. |
| Previous Message | Stephen Frost | 2016-10-14 16:19:41 | Re: Renaming of pg_xlog and pg_clog |