From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Barry Lind <barry(at)xythos(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bug?? -- Alter table drop constraint doesn't seem to work on a primary key constraint in 7.2beta2 |
Date: | 2001-11-10 20:16:41 |
Message-ID: | 1855.1005423401@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Barry Lind <barry(at)xythos(dot)com> writes:
> I was looking at the 7.2 docs online at developer.postgresql.org. The
> only example of 'drop constraint' in the text for the 'alter table'
> command shows its usage without the RESTRICT/CASCADE option.
Erroneous example fixed.
> But I still can't get it to work for me. Consider the following test case:
> create table test (col_a integer not null, col_b text);
> alter table test add constraint test_pk primary key (col_a);
> alter table test drop constraint test_pk restrict;
> psql:test.sql:8: ERROR: ALTER TABLE / DROP CONSTRAINT: test_pk does not
> exist
Looking at the code, the problem is that DROP CONSTRAINT only works with
CHECK constraints at the moment. This does seem to be adequately
documented. Improving the functionality will have to wait for some
future development cycle.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-11-11 02:58:22 | Re: compiling libpq++ on Solaris with Sun SPRO6U2 (fixed |
Previous Message | Tom Lane | 2001-11-10 18:39:19 | Re: Bug #513: union all changes char(3) column definition |