Re: tab_complete for copy(merge - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: tab_complete for copy(merge
Date
Msg-id 064da763-c86f-4c3e-b02e-7afd589b0698@eisentraut.org
Whole thread Raw
In response to Re: tab_complete for copy(merge  (jian he <jian.universality@gmail.com>)
List pgsql-hackers
On 19.11.24 14:23, jian he wrote:
> On Tue, Nov 19, 2024 at 5:20 PM Kirill Reshke <reshkekirill@gmail.com> wrote:
>> On Tue, 19 Nov 2024, 14:08 jian he, <jian.universality@gmail.com> wrote:
>>> in v17, we support COPY(MERGE RETURNING)
>>> we can add tab_complete for it.
>>
>>
>> Sounds sane
>>>
>>>      /* Complete COPY ( with legal query commands */
>>>      else if (Matches("COPY|\\copy", "("))
>>> -               COMPLETE_WITH("SELECT", "TABLE", "VALUES", "INSERT
>>> INTO", "UPDATE", "DELETE FROM", "WITH");
>>> +               COMPLETE_WITH("SELECT", "TABLE", "VALUES", "INSERT
>>> INTO", "UPDATE", "DELETE FROM", "WITH", "MERGE INTO");
>>
>> MERGE INTO?
>>
> 
> per Synopsis
> https://www.postgresql.org/docs/current/sql-merge.html
> it should be "MERGE INTO".

Yes, we also complete "MERGE INTO" in other contexts.

Committed like that.




pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: [Feature Request] Schema Aliases and Versioned Schemas
Next
From: Ashutosh Bapat
Date:
Subject: Re: Difference in dump from original and restored database due to NOT NULL constraints on children