Re: Making the subquery alias optional in the FROM clause

Поиск
Список
Период
Сортировка
От Dean Rasheed
Тема Re: Making the subquery alias optional in the FROM clause
Дата
Msg-id CAEZATCV2A=W8-tMSUoHO=69jjzDyaUN7dZ6XTRuhC7r_awBVEg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Making the subquery alias optional in the FROM clause  (Zhihong Yu <zyu@yugabyte.com>)
Ответы Re: Making the subquery alias optional in the FROM clause
Список pgsql-hackers
On Sat, 9 Jul 2022 at 12:24, Zhihong Yu <zyu@yugabyte.com> wrote:
>
>  It seems the code would be more readable if you keep the assignment in else block below:
>
> +                   else if (rte->rtekind == RTE_SUBQUERY ||
> +                            rte->rtekind == RTE_VALUES)
>                         continue;
> -                   rtename = rte->join_using_alias->aliasname;
>                 }
> -               else
> -                   rtename = rte->eref->aliasname;
>
> because rtename would be assigned in the `rte->rtekind == RTE_JOIN` case.
>

But then it would need 2 else blocks, one inside the rte->alias ==
NULL block, for when rtekind is not RTE_JOIN, RTE_SUBQUERY or
RTE_VALUES, and another after the block, for when rte->alias != NULL.
I find it more readable this way.

Regards,
Dean



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Dean Rasheed
Дата:
Сообщение: Re: Use extended statistics to estimate (Var op Var) clauses
Следующее
От: Graham Leggett
Дата:
Сообщение: Re: [PATCH] Log details for client certificate failures