Re: Todo "claim": psql tab completion on schema names - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Todo "claim": psql tab completion on schema names
Date
Msg-id 1045354231.12011.23.camel@jester
Whole thread Raw
In response to Todo "claim": psql tab completion on schema names  (Ian Barwick <barwick@gmx.net>)
Responses Re: Todo "claim": psql tab completion on schema names
List pgsql-hackers
On Sat, 2003-02-15 at 18:53, Ian Barwick wrote:
> I have been playing around with psql's "tab-completion.c" and have
> something approaching a sane solution for tab expansion of
> schema names. As this seems to fall under the todo item "Allow psql to do
> table completion for SELECT * FROM schema_part and table completion for
> SELECT * FROM schema_name" I would like if possible to "claim" this, at
> least for a week or so.

I've been debating a mechanism which could build tab completion tables
based on the documentation for a while now -- and was going to give it a
try next week.  If it works, that file would essentially disappear.

It doesn't really change what happens, just the approach.  The end goal
being a backend independent psql.

> In this respect couple of general questions:
> - is there any reason why tab expansion of slash commands is
>   only implemented in a few cases? E.g. for \d but not \di ?
> . is there any requirement to maintain any kind of backwards
>   compatibilty to pre 7.3 clients?

Post 7.3 launch most of these cases were cleaned up, not to say some
weren't missed. You might want to take a look at CVS-TIP sources.  Feel
free to send in patches for ones that have been missed.

> - pg_catalog.pg_table_is_visible() works on non-table relations
>   as well, right?

I would assume so, but haven't checked.

--
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

pgsql-hackers by date:

Previous
From: Ian Barwick
Date:
Subject: Todo "claim": psql tab completion on schema names
Next
From: Ian Barwick
Date:
Subject: Re: Todo "claim": psql tab completion on schema names