| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| 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-10 06:24:29 |
| Message-ID: | 7745.1328855069@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. Also, if it is useful, people will expect it to work in more
places than just the first word after SELECT --- for instance, somebody
who didn't realize what a kluge it was would expect it to also work
right after a top-level comma after SELECT. Or probably after a left
parenthesis in the SELECT list. Etc.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-02-10 08:32:46 | Re: xlog location arithmetic |
| Previous Message | Tom Lane | 2012-02-09 23:21:58 | Patch: fix pg_dump for inherited defaults & not-null flags |