Inconsistent application of [, ...] in documentation

Поиск
Список
Период
Сортировка
От Oliver Rice
Тема Inconsistent application of [, ...] in documentation
Дата
Msg-id CAKYAq67vavWsuaPGwqmT7K7n1wPEGZZxSKv4LH_dDG0j08q04A@mail.gmail.com
обсуждение исходный текст
Ответы Re: Inconsistent application of [, ...] in documentation  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-bugs
GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER }    [, ...] | ALL [ PRIVILEGES ] }    ON { [ TABLE ] table_name [, ...]         | ALL TABLES IN SCHEMA schema_name [, ...] }    TO role_specification [, ...] [ WITH GRANT OPTION ]

Relevant Extract:
"ALL TABLES IN SCHEMA schema_name [, ...]"

Correct Usage:
"ALL TABLES IN SCHEMA public, api_v1"
Incorrect Usage:
"ALL TABLES IN SCHEMA public, ALL TABLES IN SCHEMA api_v1"


Variant B:
GRANT { EXECUTE | ALL [ PRIVILEGES ] } ON { { FUNCTION | PROCEDURE | ROUTINE } routine_name [ ( [ [ argmode ] [ arg_name ] arg_type [, ...] ] ) ] [, ...] | ALL { FUNCTIONS | PROCEDURES | ROUTINES } IN SCHEMA schema_name [, ...] } TO role_specification [, ...] [ WITH GRANT OPTION ]

Relevant Extract:
"( [ [ argmode ] [ arg_name ] arg_type [, ...] ] )"

Correct Usage:
"( first_param TEXT, second_param TEXT )"
Incorrect Usage:
"( first_param TEXT, TEXT)"

--
So in Variant A, "[, ...]" is intended to apply to the immediately preceding token but in variant B it is intended to apply to all preceding tokens in the same group.

Thank you,
Oliver








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

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: Inconsistent application of [, ...] in documentation