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

Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

From: Dave Page <dpage(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: NikhilS <nikkhils(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Boonchai <boonchai(at)xsidekick(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgadmin-support(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)
Date: 2007-12-20 08:27:35
Message-ID: 476A2777.5030807@postgresql.org (view raw or flat)
Thread:
Lists: pgadmin-supportpgsql-bugs
Tom Lane wrote:
>> We use the data in various UI elements as well as for reverse
>> engineering the SQL - it's easier to get it broken down than to parse it
>> back out of the complete definition.
> 
> Seems like all the more argument for having functions that extract
> single pieces of information, rather than several pieces (especially
> if some pieces get left off when default).

Well it might well have been if the pgAdmin code didn't already work and 
it wasn't so close to release :-)

> For the moment I've reverted pg_get_indexdef() to its prior behavior
> of printing only the index column key or expression when colno!=0.
> We can look at having another function to do the other thing in 8.4.

Thanks.

/D

In response to

Responses

pgsql-bugs by date

Next:From: ChrisDate: 2007-12-20 09:04:32
Subject: BUG #3830: Error during Installation (german)
Previous:From: Iuri SampaioDate: 2007-12-20 05:38:37
Subject: Re: ltree installation error

pgadmin-support by date

Next:From: Mike BlackwellDate: 2007-12-20 19:19:57
Subject: Build only pgagent?
Previous:From: Tom LaneDate: 2007-12-20 00:27:51
Subject: Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

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