Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases
Дата
Msg-id ZVwg9AP4Zvj3RR1J@momjian.us
обсуждение исходный текст
Ответ на Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-docs
Дерево обсуждения 
On Mon, Nov 20, 2023 at 07:19:39PM -0700, David G. Johnston wrote:
> The placement in the numbered listing section feels wrong, I am OK with
> the wording.  It should be down in the clause details.
> 
> FOR lock_strength [ OF from_reference [, ...] ] [ NOWAIT | SKIP LOCKED ]  --
> need to change this spot to match
> 
> where lock_strength can be one of
> 
> [...]
> 
> + and from_reference must be a table alias or non-hidden table_name referenced
> in the FROM clause.
> 
> For more information on each [...]

Ah, good point.  I was searching for "FOR UPDATE" so I missed that
section;  updated patch attached.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.
Вложения

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

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases