Re: Column property / Drop constraint
От | Dave Page |
---|---|
Тема | Re: Column property / Drop constraint |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B825A221@mail.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Column property / Drop constraint (Jean-Michel POURE <jm.poure@freesurf.fr>) |
Ответы |
Re: Column property / Drop constraint
|
Список | pgadmin-hackers |
> -----Original Message----- > From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr] > Sent: 26 May 2003 17:17 > To: pgadmin-hackers@postgresql.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.
В списке pgadmin-hackers по дате отправления: