At 19:50 14/05/01 -0700, Stephan Szabo wrote:
>
>If it's $2 in the parent,
>but the child already has a $2 defined, what should be done? The
>reason this affects drop constraint is knowing what to drop in the
>child. If you drop $2 on the parent, what constraint(s) on the child
>get dropped?
>
It is worth considering skipping the entire 'copy to children' approach?
Something like:
pg_constraints(constraint_id, constraint_name, constraint_details....)
pg_relation_constraints(rel_id, constraint_id)
Then, when we drop constraint 'FRED', the relevant rows of these tables are
deleted. There is only ever one copy of the constraint definition.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
