Query execution order - Mailing list pgadmin-hackers

From Miha Radej
Subject Query execution order
Date
Msg-id 6.0.0.14.0.20031216132427.027141b0@mail.over.net
Whole thread Raw
In response to Re: os x port  (Adam H.Pendleton <fmonkey@fmonkey.net>)
Responses Re: Query execution order
List pgadmin-hackers
Hi!

I've been playing a bit with my frinends' tables and I wanted to remove an
existing unique constraint and add a primary key with the same name.
However, instead of first removing an existing constraint and then adding a
new one, I added the primary key and then deleted the unique constraint.
When I hit OK I got a pgsql error, telling me that a relation with that
name already exists.

The SQL tag had these queries:
ALTER TABLE uporabniki ADD CONSTRAINT uporabniki_primary_key_key PRIMARY
KEY (primary_key);
ALTER TABLE uporabniki DROP CONSTRAINT uporabniki_primary_key_key;

Is it possible for pgAdmin to reorder the queries so that the drop queries
are first and all the rest follow? Or if it could at least check for
existing constraint names?


Thanks and best regards,
Miha



pgadmin-hackers by date:

Previous
From: Adam H.Pendleton
Date:
Subject: Re: building wxPython on OS X
Next
From: Andreas Pflug
Date:
Subject: Re: Query execution order