Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE - Mailing list pgsql-hackers

From vignesh C
Subject Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE
Date
Msg-id CALDaNm2vsdn0ihSvYCTMBZkMWqQZ1jLYD+o5vqKULM0vRnjwxg@mail.gmail.com
Whole thread Raw
In response to Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE  (Melih Mutlu <m.melihmutlu@gmail.com>)
Responses Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE
Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE
List pgsql-hackers
On Tue, 6 Dec 2022 at 20:42, Melih Mutlu <m.melihmutlu@gmail.com> wrote:
>
> Hi Vignesh,
>
> Looks like the patch needs a rebase.

Rebased

> Also one little suggestion:
>
>> + if (ends_with(prev_wd, ')'))
>> + COMPLETE_WITH(Alter_routine_options, "CALLED ON NULL INPUT",
>> +  "RETURNS NULL ON NULL INPUT", "STRICT", "SUPPORT");
>
>
> What do you think about gathering FUNCTION options as you did with ROUTINE options.
> Something like the following would seem nicer, I think.
>
>> #define Alter_function_options \
>> Alter_routine_options, "CALLED ON NULL INPUT", \
>>
>> "RETURNS NULL ON NULL INPUT", "STRICT", "SUPPORT"

I did not make it as a macro for alter function options as it is used
only in one place whereas the others were required in more than one
place.
The attached v4 patch is rebased on top of HEAD.

Regards,
Vignesh

Attachment

pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Split index and table statistics into different types of stats
Next
From: Nathan Bossart
Date:
Subject: Re: wake up logical workers after ALTER SUBSCRIPTION