Search Postgresql Archives

Re: Self referencing composite datatype

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 7, 2013 at 11:38 PM, Alban Hertroys <haramrae@xxxxxxxxx> wrote:
> On Aug 8, 2013, at 4:11, Sergey Konoplev <gray.ru@xxxxxxxxx> wrote:
>> create table node as (
>>  id integer primary key,
>>  r integer, s integer,
>>  children integer[]
>> );
>>
>> and check integrity by triggers.
>
>
> Or, instead of attempting to reference all child nodes from the parent, reference the parent node from each child node.
> That's been supported in PG versions like forever and can be queried fairly efficiently using recursive CTE's since PG 9.

That particular moment I thought it was about graphs. Later OP
mentioned tree, so yes, it is better to use parent reference here.

-- 
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray.ru@xxxxxxxxx


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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux