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

Re: inconsitent tab completion in psql

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>,pgsql-bugs(at)postgresql(dot)org
Subject: Re: inconsitent tab completion in psql
Date: 2005-01-23 17:01:34
Message-ID: 20050123170134.GA19315@dcc.uchile.cl (view raw or flat)
Thread:
Lists: pgsql-bugs
On Sun, Jan 23, 2005 at 11:01:14AM -0500, Bruce Momjian wrote:

> The reason this happens is because both ALTER OPERATOR and ALTER
> OPERATOR CLASS are supported so for the third word you would have to do
> tab complete only when the C-L-A-S-S is unique.  I suppose you could say
> as soon as they type 'C' it can't match an operator name but it hardly
> seems worth the complexity.

Maybe you could add, to the query that extract operator names to
complete, a UNION clause with the constant CLASS.  So tab completion for
ALTER OPERATOR would show both the operators and the CLASS constant.
But beware of

ALTER OPERATOR ~<tab>

you'd have to add a LIKE clause to the CLASS arm of the union to prevent
that, I think.

-- 
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Para tener más hay que desear menos"

In response to

pgsql-bugs by date

Next:From: Florin BorsaDate: 2005-01-23 17:39:05
Subject: BUG #1436: not null condition is not respected
Previous:From: Bruce MomjianDate: 2005-01-23 16:01:14
Subject: Re: inconsitent tab completion in psql

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