| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
| Subject: | Re: psql tab completion for SELECT |
| Date: | 2012-02-13 21:21:48 |
| Message-ID: | 1329168108.5373.8.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tor, 2012-02-09 at 23:02 +0100, Dimitri Fontaine wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Make tab-completion complete also function names – like: SELECT
> > pg_get<tab><tab> to see all functions that start with pg_get.
> >
> > Make tab-completion work for columns in SELECT. I know that when writing
> > SELECT clause, psql doesn’t know which table it will deal with, but it
> > could search through all the columns in database.
> >
> > That seems pretty useful, and it's more or less a one-line change, as in
> > the attached patch.
>
> Does that includes support for completing SRF functions in the FROM clause?
No, that's an entirely different issue.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-02-13 21:25:59 | Re: psql tab completion for SELECT |
| Previous Message | Jay Levitt | 2012-02-13 20:36:33 | Re: Bugs/slowness inserting and indexing cubes |