Re: [PATCH] Feature improvement for CLOSE, FETCH, MOVE tab completion

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Shinya11(dot)Kato(at)nttdata(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Feature improvement for CLOSE, FETCH, MOVE tab completion
Date: 2021-01-06 02:13:26
Message-ID: CAD21AoBiGkvFpizGAWt-8mQEja3_Afu0pjn09vR1Gk7d+zj_Cw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 5, 2021 at 6:08 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>
>
> + COMPLETE_WITH_QUERY(Query_for_list_of_cursors
> + " UNION SELECT 'ABSOLUTE'"
> + " UNION SELECT 'BACKWARD'"
> + " UNION SELECT 'FORWARD'"
> + " UNION SELECT 'RELATIVE'"
> + " UNION SELECT 'ALL'"
> + " UNION SELECT 'NEXT'"
> + " UNION SELECT 'PRIOR'"
> + " UNION SELECT 'FIRST'"
> + " UNION SELECT 'LAST'"
> + " UNION SELECT 'FROM'"
> + " UNION SELECT 'IN'");
>
> This change makes psql unexpectedly output "FROM" and "IN" just after "FETCH".

I think "FROM" and "IN" can be placed just after "FETCH". According to
the documentation, the direction can be empty. For instance, we can do
like:

postgres(1:7668)=# begin;
BEGIN

postgres(1:7668)=# declare test cursor for select relname from pg_class;
DECLARE CURSOR

postgres(1:7668)=# fetch from test;
relname
--------------
pg_statistic
(1 row)

postgres(1:7668)=# fetch in test;
relname
---------
pg_type
(1 row)

Regards,

--
Masahiko Sawada
EnterpriseDB: https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2021-01-06 02:33:39 Re: [PATCH] Feature improvement for CLOSE, FETCH, MOVE tab completion
Previous Message Andres Freund 2021-01-06 02:02:29 logical replication worker accesses catalogs in error context callback