Re: Tab completion for CREATE TYPE

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Tab completion for CREATE TYPE
Date: 2019-05-14 06:58:14
Message-ID: CA+hUKG+ojKTKw=aG6QU=VmPMc8Sq7nM4Ah7fk1e+g1YngCVNmg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 14, 2019 at 6:18 PM Kyotaro HORIGUCHI
<horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> I played with this a bit and found that "... (attr=[tab]" (no
> space between "r" and "=") complets with '='. Isn't it annoying?
>
> Only "UPDATE hoge SET a=[tab]" behaves the same way among
> existing completions.

Hmm. True. Here's one way to fix that.

--
Thomas Munro
https://enterprisedb.com

Attachment Content-Type Size
0001-Tab-completion-for-CREATE-TYPE-v2.patch application/octet-stream 2.2 KB
0002-Fix-tab-completion-of-UPDATE-v2.patch application/octet-stream 846 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-05-14 07:11:53 Re: ERROR: tuple concurrently updated when modifying privileges
Previous Message Michael Paquier 2019-05-14 06:49:50 Re: Caveats from reloption toast_tuple_target