pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: gmb <gmbouwer@gmail.com>
To: pgsql-sql@postgresql.org
Subject: Re: UNNEST result order vs Array data
Date: Thu, 20 Jun 2013 05:32:24 -0700 (PDT)
Message-ID: <1371731544016-5760107.post@n5.nabble.com> (raw)
In-Reply-To: <51C2F177.8020808@dalibo.com>
References: <1371724857304-5760087.post@n5.nabble.com>
<51C2DD42.4000002@dalibo.com>
<1371726033207-5760092.post@n5.nabble.com>
<51C2F177.8020808@dalibo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
>> The best, which you won't
>> like, is to wait for 9.4 where unnest() will most likely have a WITH
>> ORDINALITY option and you can sort on that.
The fact that this type of thing is on the 9.4 roadmap indicates (to me, in
any case) that there are problems with the UNNEST functionality in the
current version (I'm running 9.2).
Thanks Vik, I'll take a look at the implementation you suggested.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/UNNEST-result-order-vs-Array-data-tp5760087p5760107.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
view thread (9+ messages) latest in thread
Message-ID: <1371731544016-5760107.post@n5.nabble.com>
Permalink: ../1371731544016-5760107.post@n5.nabble.com/
Also on: postgresql.org/message-id/1371731544016-5760107.post@n5.nabble.com
reply
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-sql@postgresql.org
Cc: gmbouwer@gmail.com
Subject: Re: UNNEST result order vs Array data
In-Reply-To: <1371731544016-5760107.post@n5.nabble.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