From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Tim Knowles" <tim(at)ametco(dot)co(dot)uk> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #785: 7.3b2 : Possible Inconsistency with DROP INDEX ... CASCADE and DROP CONSTRAINT |
Date: | 2002-09-30 14:50:55 |
Message-ID: | 21221.1033397455@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Tim Knowles" <tim(at)ametco(dot)co(dot)uk> writes:
> ... I do though think the error message could do with a slight change
> of wording from:
> ERROR: Cannot drop index t1_pkey because constraint c1 on table t1 requires
> it
> You may drop constraint c1 on table t1 instead
> to:
> ERROR: Cannot drop index t1_pkey because constraint c1 on table t1 requires
> it
> To drop index t1_pkey you will need to drop the constraint c1 from
> table t1 first
Well, no, because the second message is not accurate at all for this
situation. The hint to drop the constraint *instead* is perfectly
correct; when you do that the index will go away too.
I was thinking more of rewording the first line, perhaps like this:
> ERROR: Cannot drop index t1_pkey because it is part of constraint c1 on table t1
but wasn't completely satisfied with that either.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Knowles | 2002-09-30 15:39:11 | Re: Bug #785: 7.3b2 : Possible Inconsistency with DROP INDEX ... CASCADE and DROP CONSTRAINT |
Previous Message | Tim Knowles | 2002-09-30 13:27:12 | Bug #785: 7.3b2 : Possible Inconsistency with DROP INDEX ... CASCADE and DROP CONSTRAINT |