Re: Tree structure

From: Rémi Cura <remi(dot)cura(at)gmail(dot)com>
To: Kaare Rasmussen <kaare(at)jasonic(dot)dk>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Tree structure
Date: 2013-10-10 16:15:06
Message-ID: CAJvUf_uqRXE-Osc5Yp7F7GZK8NsVV6qaGJiSF0A_97Omk3SzAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hey sorry if my answer is stupid,
but there is an extension for array, even if it is limited to int (but int
could be indexes of row)
It's named http://www.postgresql.org/docs/9.3/static/intarray.html
It provides essential function, although lacking some (I re-implemented
union of array with disjoint result).
I think this extension uses indexes

Cheers,
Rémi-C

2013/10/10 Kaare Rasmussen <kaare(at)jasonic(dot)dk>

> Hi Merlin
>
> On Thu, Oct 10, 2013 at 1:00 AM, Kaare Rasmussen <kaare(at)jasonic(dot)dk>
>> wrote:
>>
>>> I'm quite surprised there seem to be no way in core to treat an array as
>>> an
>>> array. Using @> treats it as a set, AFAICT.
>>>
>> can you elaborate on that?
>>
>> merlin
>>
>
> To me, an array is a vector (or a vector of vectors). So I'm looking for
> an operator where
>
> ARRAY[1,4,3] doesn't contain ARRAY[3,1] and
> ARRAY[2,7] isn't contained by ARRAY[1,7,4,2,6] (but ARRAY[1,7,4] is)
>
> IOW order matters to me, but not to the array operators mentioned in
> http://www.postgresql.org/**docs/9.3/static/functions-**array.html<http://www.postgresql.org/docs/9.3/static/functions-array.html>.
> Note that index support is important.
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-general<http://www.postgresql.org/mailpref/pgsql-general>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kaare Rasmussen 2013-10-10 16:33:23 Re: Tree structure
Previous Message Rob Richardson 2013-10-10 15:03:48 Why doesn't update syntax match insert syntax?