From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: array support patch phase 1 patch |
Date: | 2003-06-02 15:39:52 |
Message-ID: | 8709.1054568392@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Joe Conway <mail(at)joeconway(dot)com> writes:
> Kris Jurka wrote:
>> I was trying formulate a way to make a function which will explode an
>> array into a resultset composed of the index and value.
> I submitted a function that would do this, array_values(), but it was
> rejected. See:
> http://archives.postgresql.org/pgsql-hackers/2002-12/msg00453.php
> Perhaps we should revisit that decision before feature freeze for 7.4?
Kris' example didn't seem at all compelling to me, since the basic query
design was wrong anyway if he hopes to deal with multiple-column foreign
keys. You can't have just one instance of pg_attribute being joined to,
unless you are planning to execute the query again for each column ---
and in that case the tests might as well be like "attnum = conkey[1]",
next time "attnum = conkey[2]", etc.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-06-02 15:41:39 | Re: SQL99 CREATE TABLE ... (LIKE parent_table) |
Previous Message | Bruce Momjian | 2003-06-02 15:38:43 | Re: LIKE <subtable> (second attempt) |