From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | Dirar Abu Kteish <dirar(dot)kteish(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1601: removing columns |
Date: | 2005-04-16 23:18:19 |
Message-ID: | c2d9e70e05041616181dc62270@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 4/16/05, Dirar Abu Kteish <dirar(dot)kteish(at)gmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1601
> Logged by: Dirar Abu Kteish
> Email address: dirar(dot)kteish(at)gmail(dot)com
> PostgreSQL version: PostgreSQL 8.0.
> Operating system: Windows XP SP2
> Description: removing columns
> Details:
>
> I had a "bug" when I was trying to remove one column from a table, let's say
> I had something like this:
> field called Field_1, I removed it, then I clicked on add (without exiting
> the properties, the OK button), and added the same "Field_1" column, then it
> reports an error that the field already exist. Maybe it would be better that
> when removing fields and clicking on Add, to ask whether to apply the
> changes, or when adding the same filed name to ask if to apply the removing
> action.
>
i don't think it's a postgresql bug but a pgAdmin (or whatever gui
interface you are using) one.
regards,
Jaime Casanova
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-04-17 00:50:10 | Re: BUG #1600: Interrupt routine causes libPQ call to fail w/o error |
Previous Message | moch sidhki | 2005-04-16 18:36:56 | HELP MEEEEEEEEE |