Re: PL/Python adding support for multi-dimensional arrays

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, 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:18:01
Message-ID: 357678e5-96bd-00d6-fbee-9f5a5aa09b39@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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? I'm not sure they would
automatically be considered as tuples (unlike something that extends
tuples, such as namedtuples).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2016-10-14 16:19:41 Re: Renaming of pg_xlog and pg_clog
Previous Message Robert Haas 2016-10-14 16:17:25 Re: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits.