Re: some more error location support

Поиск
Список
Период
Сортировка
Искать
От
Fabien COELHO
Тема
Re: some more error location support
Дата
Msg-id
alpine.DEB.2.21.1808291637310.14012@lancre
Ответ на
Список
Дерево обсуждения
some more error location support Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: some more error location support Fabien COELHO <coelho@cri.ensmp.fr>
Re: some more error location support Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: some more error location support Fabien COELHO <coelho@cri.ensmp.fr>
Re: some more error location support Fabien COELHO <coelho@cri.ensmp.fr>
Re: some more error location support Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: some more error location support Fabien COELHO <coelho@cri.ensmp.fr>
Re: some more error location support Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: some more error location support Fabien COELHO <coelho@cri.ensmp.fr>
Re: some more error location support Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: some more error location support Fabien COELHO <coelho@cri.ensmp.fr>
Re: some more error location support Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

>> The majority rule (34 make & 22 free) suggest that it is more often use
>> than not. I'd suggest to stick to that for consistency & homogeneity.
>
> But it's consistently not used in DDL command implementations, only in
> normal query parsing.

I try to avoid complicated (context-sensitive) rules when I can, esp as 
some functions may be called from DDL and DML.

But fine with me.

-- 
Fabien.

В списке pgsql-hackers по дате отправления
От: Fabien COELHO
Дата:
От: Chapman Flack
Дата:
FAQ