| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Updating system catalogs after a tuple deletion |
| Date: | 2001-05-15 03:24:46 |
| Message-ID: | 3.0.5.32.20010515132446.009f0100@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2001-05-15 03:26:55 | RE: Updating system catalogs after a tuple deletion |
| Previous Message | Tom Lane | 2001-05-15 03:10:44 | Re: Updating system catalogs after a tuple deletion |