At 14:05 19/02/02 -0800, Stephan Szabo wrote:
>
>Check constraints and not null I believe are inherited by default.
>But I just thought of a case that won't dump and restore the same as it
>was originally made because we support ONLY on alter table add constraint.
>
>create table z(a int);
>create table z2() inherits(z);
>alter table only z add constraint foo1 check(a>4);
>
>will make z have a constraint on a but not z2 and the check will get
>dumped as part of z's definition which will restore with z2 having
>the check.
This brings to mind a couple of questions:
1. Do you have plans to support inhertiance of PK constraints?
2. Does/will DROP CONSTRAINT support ONLY?
----------------------------------------------------------------
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 |/
