| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Thom Brown <thom(at)linux(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: string_to_array with an empty input string |
| Date: | 2010-08-11 17:58:57 |
| Message-ID: | 4C62E4E1.4000505@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/11/2010 01:54 PM, David E. Wheeler wrote:
> On Aug 11, 2010, at 10:53 AM, Robert Haas wrote:
>
>>> Iterating through an array with plpgsql, for example, is more clunky
>>> than it should be.
>> Really?
>>
>> FOR var IN SELECT UNNEST(arr) LOOP ... END LOOP
>>
>> I mean, doing everything is sort of clunky in PL/pgsql, but this
>> doesn't seem particularly bad as PL/pgsql idioms go.
> That tends to over-flatten if you have nested arrays and just want to iterate over the top level. In that case you must use generate_subscripts().
for i in array_lower(myarray,1) .. array_upper(myarray,1) loop ...
works well
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-08-11 17:59:54 | Re: string_to_array with an empty input string |
| Previous Message | David E. Wheeler | 2010-08-11 17:54:27 | Re: string_to_array with an empty input string |