From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | depesz(at)depesz(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Would it be possible to add functions to tab-completion in psql? |
Date: | 2022-08-17 05:33:25 |
Message-ID: | ec6347a9-f218-2e6c-49d0-e4c8ea5665fb@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 16.08.22 16:14, hubert depesz lubaczewski wrote:
> Specifically, I'd ask what is the harm of increasing what tab completion
> can do by a lot - for example, make it tab-complete fields from all
> tables. And make it possible to tab-complete column name anywhere in
> where clause. But function name in select would be (for me(!)) great
> first step, and I can't really see the drawbacks, aside from using
> developer time to work on it.
I think in this case it would be straightforward to write a patch and
then we can see what the experience is in practice. I agree this could
be a useful feature.
From | Date | Subject | |
---|---|---|---|
Next Message | Rama Krishnan | 2022-08-17 08:53:41 | Sub:column "" is of type bigint but expression is of type character varying |
Previous Message | Tatsuo Ishii | 2022-08-17 05:16:54 | Re: Regarding availability of 32bit client drivers for postgresql 13/14 |