From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Christoph Heiss <christoph(at)c8h4(dot)io> |
Cc: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Mikhail Gribkov <youzhick(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] psql: Add tab-complete for optional view parameters |
Date: | 2023-08-08 08:17:51 |
Message-ID: | CAEZATCW+0y7Ut1DY3MuKF-HF-3oToOCfUi33rnuWNYZAa2V84Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 7 Aug 2023 at 19:49, Christoph Heiss <christoph(at)c8h4(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-08-08 08:20:42 | Re: Handle infinite recursion in logical replication setup |
Previous Message | Drouvot, Bertrand | 2023-08-08 08:16:37 | Re: WIP: new system catalog pg_wait_event |