Re: Bug in SQL script for indexes - Mailing list pgadmin-hackers

From Guillaume Lelarge
Subject Re: Bug in SQL script for indexes
Date
Msg-id 1346450230.1981.11.camel@localhost.localdomain
Whole thread Raw
In response to Bug in SQL script for indexes  (Erwin Brandstetter <brandstetter@falter.at>)
List pgadmin-hackers
On Mon, 2012-08-27 at 19:19 +0200, Erwin Brandstetter wrote:
> Aloha!
>
> The SQL script for indexes incorrectly prepends the index name with the table name of the involved table - instead of
theschema name where the index  
> lives.
>
> Demo to reproduce:
> I say:
>
>      CREATE TABLE x(name text);
>      CREATE INDEX name_idx ON x (name);
>
> pgAdmin says:
>      -- Index: x.name_idx
>
>      -- DROP INDEX x.name_idx;
>
>      CREATE INDEX name_idx
>        ON x
>        USING btree
>        (name COLLATE pg_catalog."default" );
>
> Must be:
>
>      -- Index: name_idx
>
>      -- DROP INDEX name_idx;
>      ...
>
> Or:
>
>      -- Index: public.name_idx
>
>      -- DROP INDEX public.name_idx;
>      ...
>
> http://code.pgadmin.org/trac/ is still down, so I did not file a ticket.
>

Same indexes issue. The patch I have fixes this.


--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com



pgadmin-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: Re: Items missing from some context menus in object browser of v1.16 beta4
Next
From: Guillaume Lelarge
Date:
Subject: Re: pgAdmin III commit: Lots of work on domains, and check constraints