Query execution order

Поиск
Список
Период
Сортировка
От Miha Radej
Тема Query execution order
Дата
Msg-id 6.0.0.14.0.20031216132427.027141b0@mail.over.net
обсуждение исходный текст
Ответ на Re: os x port  (Adam H.Pendleton <fmonkey@fmonkey.net>)
Ответы Re: Query execution order  (Andreas Pflug <pgadmin@pse-consulting.de>)
Список 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 по дате отправления:

Предыдущее
От: Adam H.Pendleton
Дата:
Сообщение: Re: building wxPython on OS X
Следующее
От: Andreas Pflug
Дата:
Сообщение: Re: Query execution order