Skip site navigation (1) Skip section navigation (2)

Re: Bug in SQL script for indexes

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Erwin Brandstetter <brandstetter(at)falter(dot)at>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Bug in SQL script for indexes
Date: 2012-08-31 21:57:10
Message-ID: 1346450230.1981.11.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: 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 the schema 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



In response to

pgadmin-hackers by date

Next:From: Guillaume LelargeDate: 2012-08-31 21:57:22
Subject: Re: pgAdmin III commit: Lots of work on domains, and check constraints
Previous:From: Guillaume LelargeDate: 2012-08-31 21:55:28
Subject: Re: Re: Items missing from some context menus in object browser of v1.16 beta4

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group