Re: Support for negative index values in array fetching - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: Support for negative index values in array fetching
Date
Msg-id A343FC93-9677-47C0-AF08-561C3BCD8AA9@phlo.org
Whole thread Raw
In response to Support for negative index values in array fetching  ("Valtonen, Hannu" <hannu.valtonen@hut.fi>)
Responses Re: Support for negative index values in array fetching  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Jan2, 2011, at 11:45 , Valtonen, Hannu wrote:
> I ran into the problem of getting the last n elements out of an array and while some workarounds do exist:
> (http://stackoverflow.com/questions/2949881/getting-the-last-element-of-a-postgres-array-declaratively) I was still
annoyedthat I couldn't just ask for the last n values in an array Python/Perl style. 
>
> Here's a patch to add support for negative index values in fetching elements from an array.

That won't work. In SQL, array indices don't necessarily start with 0 (or 1, or *any*
single value). Instead, you can each dimension's lower and upper bound for index values
with array_lower() and array_upper().

Here's an example

fgp=> do $$ declare a text[]; begin   a[-1] := 'foo';   a[0] := 'bar';   raise notice 'a[-1] == %', a[-1]; end
$$ language 'plpgsql' ;

This will raise the notice 'a[-1] == foo'!

The only way around that would be to introduce magic constants "lower", "upper" that
can be used within index expressions and evaluate to the indexed dimension's lower
and upper bound. You'd then use
 my_array[upper], my_array[upper-1], ...

to refer to the last, second-to-last, ... element in the array. Actually doing this
could get pretty messy, though - not sure if it's really worth the effort...

best regards,
Florian Pflug



pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Extension upgrade, patch v0: debug help needed
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Basic foreign table support.