From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Matthew Wakeling <matthew(at)flymine(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: plpgsql arrays |
Date: | 2009-04-03 15:18:33 |
Message-ID: | b42b73150904030818y448b72bdl8892e3839fd23955@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, Apr 3, 2009 at 11:15 AM, Matthew Wakeling <matthew(at)flymine(dot)org> wrote:
> On Fri, 3 Apr 2009, Merlin Moncure wrote:
>>
>> select array(SELECT location FROM location, gene WHERE
>> location.subjectid = gene.id ORDER BY objectid, intermine_start,
>> intermine_end)) into genes;
>
> Yeah, that works nicely.
>
>> this will make array of location records. when you access the records
>> to do the merge, make sure to use () noation:
>>
>> if (genes[x]).field > something then
>
> How is that different to genes[x].field?
ah, it isn't...in many cases where you access composite type fields,
() is required (especially in query). it isn't here, so you can
safely leave it off.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2009-04-03 15:52:36 | Re: Rewriting using rules for performance |
Previous Message | Matthew Wakeling | 2009-04-03 15:15:32 | Re: plpgsql arrays |