Re: [PATCH] psql: Add tab-complete for optional view parameters

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: David Zhang <david(dot)zhang(at)highgo(dot)ca>
Cc: Christoph Heiss <christoph(at)c8h4(dot)io>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] psql: Add tab-complete for optional view parameters
Date: 2023-11-23 11:07:33
Message-ID: CAEZATCWOrEdpJ_e7L6+JPQDpMaJ2VFHm9M7wc6i94uFow7rEJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 14 Aug 2023 at 18:34, David Zhang <david(dot)zhang(at)highgo(dot)ca> wrote:
>
> it would be great to switch the order of the 3rd and the 4th line to make a
> better match for "CREATE" and "CREATE OR REPLACE" .
>

I took a look at this, and I think it's probably neater to keep the
"AS SELECT" completion for CREATE [OR REPLACE] VIEW xxx WITH (*)
separate from the already existing support for "AS SELECT" without
WITH.

A couple of other points:

1. It looks slightly neater, and works better, to complete one word at
a time -- e.g., "WITH" then "(", instead of "WITH (", since the latter
doesn't work if the user has already typed "WITH".

2. It should also complete with "=" after the option, where appropriate.

3. CREATE VIEW should offer "local" and "cascaded" after
"check_option" (though there's no point in doing likewise for the
boolean options, since they default to true, if present, and false
otherwise).

Attached is an updated patch, incorporating those comments.

Barring any further comments, I think this is ready for commit.

Regards,
Dean

Attachment Content-Type Size
v4-0001-psql-Add-tab-completion-for-view-options.patch text/x-patch 4.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2023-11-23 11:35:16 Re: WaitEventSet resource leakage
Previous Message Alexander Lakhin 2023-11-23 11:00:01 Re: Random pg_upgrade test failure on drongo