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 ZXJmpe__WfBZgKX2@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>)
Список pgsql-docs
On Mon, Nov 20, 2023 at 08:20:57PM -0700, David G. Johnston wrote:
> On Mon, Nov 20, 2023 at 8:16 PM Bruce Momjian <bruce@momjian.us> wrote:
> 
>     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.
> 
> 
> 
> WFM.

Patch applied to master.

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

  Only you can decide what is important to you.



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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [DOCS] intagg.sgml: example wrongly named and does not compile
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: [DOCS] Confusing Trigger Docs.