Re: tab_complete for copy(merge

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tab_complete for copy(merge
Date: 2024-11-19 13:23:54
Message-ID: CACJufxFemAs-XyOtm_to1MDB7qMZwi1ZiTPO3mmAB19owdL=tA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 19, 2024 at 5:20 PM Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
>
> Hi!
>
> On Tue, 19 Nov 2024, 14:08 jian he, <jian(dot)universality(at)gmail(dot)com> wrote:
>>
>> hi.
>>
>> 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".

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2024-11-19 13:29:12 Re: Changing shared_buffers without restart
Previous Message jian he 2024-11-19 13:22:43 Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints