Date: Sun, 20 Sep 2015 12:40:12 -0700 (MST)
From: dave <audiotecture@web.de>
To: pgsql-sql@postgresql.org
Message-ID: <1442778012511-5866585.post@n5.nabble.com>
In-Reply-To: 
 <CAKFQuwZaOBndHjiyD9-b2bE3y2Mbd5ttQajT4BQ48cXbZZwxrQ@mail.gmail.com>
References: <1442747556700-5866560.post@n5.nabble.com>
 <55FEBBE0.8090902@gmail.com> <1442764637710-5866579.post@n5.nabble.com>
 <CAKFQuwZaOBndHjiyD9-b2bE3y2Mbd5ttQajT4BQ48cXbZZwxrQ@mail.gmail.com>
Subject: Re: Recursive merging of overlapping arrays in a column
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Hey David,

funnny that you give me that advice because that's exactly where I came
from.

I tried analyzing a adjacence table with several disjunct graphs without
real success, so I tried concatenating the values in the Table to arrays by
grouping the ids and then aggregating the overlaping arrays to finally get
the whole set of points for each graph as an array.
I have never worked with graph functions before, so I might be missing some
elegant solution here. My feeling was simply, that it would be easier to
merge the arrays like I did in my current approach.

Regards

Dave


--
View this message in context: http://postgresql.nabble.com/Recursive-merging-of-overlapping-arrays-in-a-column-tp5866560p5866585.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql