Re: Column property / Drop constraint - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Column property / Drop constraint
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B825A221@mail.vale-housing.co.uk
Whole thread Raw
In response to Column property / Drop constraint  (Jean-Michel POURE <jm.poure@freesurf.fr>)
Responses Re: Column property / Drop constraint  (Andreas Pflug <Andreas.Pflug@web.de>)
List 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 by date:

Previous
From: Adam H.Pendleton
Date:
Subject: Re: Bootstrap
Next
From: "Dave Page"
Date:
Subject: Re: Gdk BadMatch with menus