Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH]Feature improvement for MERGE tab completion - Mailing list pgsql-hackers

From Shinya Kato
Subject Re: [PATCH]Feature improvement for MERGE tab completion
Date
Msg-id 5b2e2880da33f6356931beb5c0d68c84@oss.nttdata.com
Whole thread Raw
In response to Re: [PATCH]Feature improvement for MERGE tab completion  (bt22kawamotok <bt22kawamotok@oss.nttdata.com>)
Responses Re: [PATCH]Feature improvement for MERGE tab completion
List pgsql-hackers
Tree view 
On 2022-09-12 18:20, bt22kawamotok wrote:
> Other than this correction, the parts that can be put together in OR
> were corrected in fix_tab_completion_merge_v4.patch.

When I tried to apply this patch, I got the following warning, please 
fix it.
Other than that, I think everything is fine.

$ git apply fix_tab_completion_merge_v4.patch
fix_tab_completion_merge_v4.patch:38: trailing whitespace.
         else if (TailMatches("USING", MatchAny, "ON", MatchAny) ||
fix_tab_completion_merge_v4.patch:39: indent with spaces.
                  TailMatches("USING", MatchAny, "AS", MatchAny, "ON", 
MatchAny) ||
fix_tab_completion_merge_v4.patch:40: indent with spaces.
                  TailMatches("USING", MatchAny, MatchAny, "ON", 
MatchAny))
fix_tab_completion_merge_v4.patch:53: trailing whitespace.
         else if (TailMatches("WHEN", "MATCHED") ||
warning: 4 lines add whitespace errors.

-- 
Regards,

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

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: why can't a table be part of the same publication as its schema
Next
From: "Drouvot, Bertrand"
Date:
Subject: Re: Query Jumbling for CALL and SET utility statements