Thread: Bug in SQL script for indexes

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.

Regards
Erwin

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