From: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: array_reverse() |
Date: | 2009-11-02 15:06:48 |
Message-ID: | 20091102150648.GI5407@samason.me.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Nov 02, 2009 at 09:55:20AM -0500, Merlin Moncure wrote:
> On Mon, Nov 2, 2009 at 9:51 AM, Sam Mason <sam(at)samason(dot)me(dot)uk> wrote:
> > On Mon, Nov 02, 2009 at 09:20:38AM -0500, Tom Lane wrote:
> >> Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> >> > Before I go ahead and try to write a decent quality version: is there
> >> > any chance an array_reverse() function (in C) would be accepted into Pg
> >> > mainline?
> >>
> >> What would it mean for a multi-dimensional array?
> >
> > Rotating the array by 180 degrees in every dimension would give the same
> > answer for 1-dimensional arrays and give sensible answers for higher
> > dimensional arrays.
> do you think that's the typical case, or is it more common to want to
> reverse a particular slice?
I hadn't thought about that; I'm normally more concerned about making
the general case (i.e. most complicated) behave sensibly, with the
common cases being optimizations.
The problem I was solving was making 1d arrays consistent with higher
dimensional ones. As far as I can tell, if the spec is just to rotate
by 180 degrees then the implementation is pretty easy; just run through
all the elements writing them out in reverse order. Sizes and number of
dimensions can be completely ignored.
--
Sam http://samason.me.uk/
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-11-02 15:09:14 | Re: array_reverse() |
Previous Message | Ivan Sergio Borgonovo | 2009-11-02 15:04:41 | Re: pk vs unique not null differences between 8.3.4 and 8.3.8 |