Jonathan Knopp <[EMAIL PROTECTED]> writes:
> 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.
You can if you like make a view that emulates the appearance of a child
table with a common column, viz
create view childview as select child.*, parent.common
from child, parent where parent_id = parent.id;
and it would even be possible to make a rule that allows updating this
view.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
