Re: [PATCH] psql: Add tab-complete for optional view parameters - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: [PATCH] psql: Add tab-complete for optional view parameters
Date
Msg-id CAEZATCW+0y7Ut1DY3MuKF-HF-3oToOCfUi33rnuWNYZAa2V84Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] psql: Add tab-complete for optional view parameters  (Christoph Heiss <christoph@c8h4.io>)
Responses Re: [PATCH] psql: Add tab-complete for optional view parameters
List pgsql-hackers
On Mon, 7 Aug 2023 at 19:49, Christoph Heiss <christoph@c8h4.io> wrote:
>
> On Fri, Jan 06, 2023 at 12:18:44PM +0000, Dean Rasheed wrote:
> > Hmm, I don't think we should be offering "check_option" as a tab
> > completion for CREATE VIEW at all, since that would encourage users to
> > use non-SQL-standard syntax, rather than CREATE VIEW ... WITH
> > [CASCADED|LOCAL] CHECK OPTION.
>
> Left that part in for now. I would argue that it is a well-documented
> combination and as such users would expect it to turn up in the
> tab-complete as well. OTOH not against removing it either, if there are
> others voicing the same opinion ..
>

On reflection, I think that's probably OK. I mean, I still don't like
the fact that it's offering to complete with non-SQL-standard syntax,
but that seems less bad than using an incomplete list of options, and
I don't really have any other better ideas.

Regards,
Dean



pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: WIP: new system catalog pg_wait_event
Next
From: Peter Eisentraut
Date:
Subject: Re: Handle infinite recursion in logical replication setup