From: | Rémi Cura <remi(dot)cura(at)gmail(dot)com> |
---|---|
To: | Kaare Rasmussen <kaare(at)jasonic(dot)dk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tree structure |
Date: | 2013-09-23 13:16:37 |
Message-ID: | CAJvUf_u5TvyT_JF69cn6ewf+AFonhx-h3dQhbDPsjYTAwBkC8Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
BE carefull you have a number of limitation with recursive cte (I'm
thinking of update and so.)
You can work around with plpgsql but it might be painfull.
You forgot a solution :
if you need powerfull graph features,
use postgres as a database and a SPARQL speaking frontend.
It may be a bit of overkill ;-)
Cheers,
Rémi-C
2013/9/23 Kaare Rasmussen <kaare(at)jasonic(dot)dk>
> Hi Alban
>
>
> 4. Using a recursive common table expression (CTE).
>> http://www.postgresql.org/**docs/9.2/static/queries-with.**html<http://www.postgresql.org/docs/9.2/static/queries-with.html>
>>
>
> Yes, you're right. In fact that's what I'm testing a way to replace, as
> I'm not confident in the performance in all situations. My fault entirely;
> I should have told so from the start.
>
>
>
>
>
> --
> 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>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Raphael Bauduin | 2013-09-23 13:25:27 | Re: passing multiple records to json_populate_recordset |
Previous Message | Raphael Bauduin | 2013-09-23 09:31:40 | passing multiple records to json_populate_recordset |