Re: [PATCH] Added TRANSFORM FOR for COMMENT tab completion - Mailing list pgsql-hackers

From Shinya Kato
Subject Re: [PATCH] Added TRANSFORM FOR for COMMENT tab completion
Date
Msg-id ab15d09688c639d00d1013ad2f5f325d@oss.nttdata.com
Whole thread Raw
In response to Re: [PATCH] Added TRANSFORM FOR for COMMENT tab completion  (katouknl <katouknl@oss.nttdata.com>)
Responses Re: [PATCH] Added TRANSFORM FOR for COMMENT tab completion  (Ken Kato <katouknl@oss.nttdata.com>)
List pgsql-hackers
On 2021-10-14 14:30, katouknl wrote:
>> It is very good, but it seems to me that there are some tab-completion
>> missing in COMMENT command.
>> For example,
>> - CONSTRAINT ... ON DOMAIN
>> - OPERATOR CLASS
>> - OPERATOR FAMILY
>> - POLICY ... ON
>> - [PROCEDURAL]
>> - RULE ... ON
>> - TRIGGER ... ON
>> 
>> I think these tab-comletion also can be improved and it's a good
>> timing for that.
> 
> Thank you for the comments!
> 
> I fixed where you pointed out.
Thank you for the update!
I tried "COMMENT ON OPERATOR ...", and an operator seemed to be 
complemented with double quotation marks.
However, it caused the COMMENT command to fail.
---
postgres=# COMMENT ON OPERATOR "+" (integer, integer) IS 'test_fail';
ERROR:  syntax error at or near "("
LINE 1: COMMENT ON OPERATOR "+" (integer, integer) IS 'test_fail';
postgres=# COMMENT ON OPERATOR + (integer, integer) IS 'test_success';
COMMENT
---

So, I think as with \do command, you do not need to complete the 
operators.
Do you think?


-- 
Regards,

--
Shinya Kato
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [RFC] building postgres with meson
Next
From: Greg Nancarrow
Date:
Subject: Re: row filtering for logical replication