From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, 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-10 13:50:35 |
Message-ID: | CA+TgmoY7wRGgBbFhKwfASqrNOPwZwCjfm1AhL82769Xx-SyduA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 10, 2012 at 1:24 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> That seems pretty useful, and it's more or less a one-line change, as in
>> the attached patch.
>
> That seems pretty nearly entirely bogus. What is the argument for
> supposing that the word right after SELECT is a function name? I would
> think it would be a column name (from who-knows-what table) much more
> often.
It isn't necessarily, but it might be. It'd certainly be nice to type:
SELECT pg_si<TAB>
and get:
SELECT pg_size_pretty(
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-02-10 13:54:07 | Re: psql tab completion for SELECT |
Previous Message | Shigeru Hanada | 2012-02-10 13:05:42 | Re: WIP: Collecting statistics on CSV file data |