Re: Typo in PL/pgSQL trigger Example 43.4?

Поиск
Список
Период
Сортировка
От Kirk Parker
Тема Re: Typo in PL/pgSQL trigger Example 43.4?
Дата
Msg-id CANwZ8r=e47NDGBrqG2jSp=-vMgBNJONQjYc=kvppVEUQyY84Rg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Typo in PL/pgSQL trigger Example 43.4?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-docs


On Sat, Oct 7, 2023 at 1:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Sat, Oct 7, 2023 at 11:11 AM Kirk Parker <khp@equatoria.us> wrote:
>> INSERT INTO emp_audit SELECT 'D', now(), user, OLD.*; -- <= ARGUMENT IN QUESTION
>> The emp_audit table has a column named 'userid', which in actual usage
>> (next-to-last line quoted) is populated by 'user' which seems undefined in
>> the context.  Was that intended to be 'current_user', or am I missing
>> something?

> user is a valid pseudo-function:
> https://www.postgresql.org/docs/current/functions-info.html#FUNCTIONS-INFO-SESSION

Yeah, either way has the same result.  However, I wonder if we should
change this example to use current_user for clarity.  It does look
more like it's intended to be a variable or column reference than
a built-in function.


Since the previous example  on the page uses 'current_user' (which I suppose is why I didn't look further to see if 'user' was also a function), perhaps that would be a good idea.

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Typo in PL/pgSQL trigger Example 43.4?
Следующее
От: Daniel Gustafsson
Дата:
Сообщение: Re: Typo in PL/pgSQL trigger Example 43.4?