From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Erwin Brandstetter" <brandstetter(at)falter(dot)at> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Superfluous SQL statements |
Date: | 2008-01-08 15:20:56 |
Message-ID: | 937d27e10801080720i3dd0cc7fh52871d87f67409cd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On 08/01/2008, Erwin Brandstetter <brandstetter(at)falter(dot)at> wrote:
> Hi developers!
Hi Erwin,
> You have not heard a lot of me lately, and I am afraid that will not change
> substantially for some time. I am kind of swamped with other stuff.
> Anyhoo, I hope this bug report proves useful.
Sorry to hear that :-(.
> Testing pgAdmin v.1.8.1 (Jan 3 2008), rev: 6948).
> host: pg 8.2.5 on Debian Etch
> client: Windows XP.
>
> Trying to edit the default of a column with type integer[] per dialogue
> fails. I think I found the cause in the database logs. pgAdmin sends
> additional (unneeded) SQL-statements, that trigger an error.
>
> That's what it should send:
> ALTER TABLE ef.kat ALTER COLUMN pfad SET DEFAULT '{}'::integer[];
>
> That's what pgAdmin sends:
> ALTER TABLE ef.kat ALTER pfad TYPE integer[];
> ALTER TABLE ef.kat ALTER COLUMN pfad SET DEFAULT '{}'::integer[];
> COMMENT ON COLUMN ef.kat.pfad IS 'bla bla bla';
Fixed in SVN.
Thanks for the report!
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2008-01-08 16:52:52 | SVN Commit by dpage: r6983 - in trunk/pgadmin3: . pgadmin/dlg pgadmin/schema |
Previous Message | svn | 2008-01-08 15:19:03 | SVN Commit by dpage: r6982 - in branches/REL-1_8_0_PATCHES/pgadmin3: . pgadmin/schema |