From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <jm(dot)poure(at)freesurf(dot)fr>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Column property / Drop constraint |
Date: | 2003-05-26 20:33:44 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B825A221@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 26 May 2003 17:17
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Column property / Drop constraint
>
> 2) Drop constraint does not work
> It seems that the correct syntax is:
> ALTER TABLE schema.table DROP CONSTRAINT constraint
> and not
> ALTER TABLE schema.table DROP CONSTRAINT schema.constraint
My bad - should be fixed now.
Andreas - notived something odd when looking at this that I haven't
looked at further: when I added a check to a table, it re-added some of
the category sub-nodes again:
Table
Columns
Constraints (2)
Triggers
Columns
Constraints (3)
Triggers
I also had to add the check from the properties dialogue, I couldn't do
it from the context menu, though I could add a unique constraint there.
Dunno if that's related to the gtk issue...
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-05-26 20:37:21 | Re: Gdk BadMatch with menus |
Previous Message | Adam H.Pendleton | 2003-05-26 19:38:51 | Re: Bootstrap |