Message-ID: <41A7A5C2.6080800@delegated.net>
Date: Fri, 26 Nov 2004 13:53:06 -0800
From: Jonathan Knopp <pgsql@delegated.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: Re: Way to stop recursion?
References: <41A79A2A.6070606@delegated.net> <19345.1101504671@sss.pgh.pa.us>
In-Reply-To: <19345.1101504671@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
>>CREATE TABLE parent (id INT, cola CHAR(1), common CHAR(1));
>>CREATE TABLE child (id INT, parent_id INT, cola(1), common(1));
> 
>>What I need, is when "common" is changed for a parent, then that new 
>>value is reflected in "common" for all the children, ie:
>>...
>>Problem is, when "common" is changed for a child, I need the parent and 
>>all siblings to reflect that value too, ie:
> 
> Seems to me that your real problem is a bogus database layout.  If there
> should only be one "common" value for a parent and children, then only
> store one value ... that is, "common" should exist only in the parent.
> ...

Sorry, I should have mentioned that there is a lot more to the design 
that makes this replication necessary, including another two levels to 
the tree plus the ability to have orphaned children.