Re: wrong generated sql query order

From: Vasilev Max <max(at)stranger-team(dot)ru>
To: pgadmin-support(at)postgresql(dot)org
Subject: Re: wrong generated sql query order
Date: 2005-08-21 10:41:14
Message-ID: 43085A4A.30602@stranger-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Miha Radej wrote:
> hi!
>
> i had opened the table properties window and on the "columns" tab
> removed a column and immediately added a new one with the same name
> only of different type. this change failed due to a wrong sql query
> order; pgadmin had produced this
> ALTER TABLE document_data ADD COLUMN locked_by text;
> ALTER TABLE document_data DROP COLUMN locked_by;
> instead of
> ALTER TABLE document_data DROP COLUMN locked_by;
> ALTER TABLE document_data ADD COLUMN locked_by text;
>
> i am using pgadmin3 version 1.2.2 (jun 22 2005), installed from a rpm
> package provided by vasilev max. i am using suse linux 9.3 and am
> unable to build my own binaries on this machine so i cannot verify if
> this occurs on any other versions of pgadmin3.
>
> i apologize if this is old news but i didnt find anything similair in
> the mailing list archives after a quick search.
>
> cheers,
> M
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
Hi!

Unfortunately, I can not confirm this bug. Please, show me full
structure of your table.

wbr,
Vasilev Max
pgadmin3 1.2.2 (22.06.2005)
SuSE Linux 9.3 Professional x86/x86_64

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Miha Radej 2005-08-21 20:17:36 wrong generated sql query order
Previous Message Brad Langhorst 2005-08-18 18:35:27 some way to continue forward even when an error occurs