From: | Masaru Sugawara <rk73(at)sea(dot)plala(dot)or(dot)jp> |
---|---|
To: | Rod Taylor <rbt(at)rbt(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Is current_user a function ? |
Date: | 2002-11-29 12:16:23 |
Message-ID: | 20021129175301.5664.RK73@sea.plala.or.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28 Nov 2002 11:34:49 -0500
Rod Taylor <rbt(at)rbt(dot)ca> wrote:
> Force the system to use it as a function.
> select "current_user"();
On Thu, 28 Nov 2002 17:20:59 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > As for some current_*** functions, "select current_user;" seems to
> > work, but "select current_user();" doesn't .
>
> Complain to the SQL spec authors --- they mandated this peculiar keyword
> syntax for what is really a function call.
Since current_user() can be used in 7.2, I have thought it would work in 7.3 too.
I now understand it doesn't work any more -- as well, session_user(), user(),
current_date(), current_time(), current_timestamp() and etc.
Thank you, Rod and Tom.
Regards,
Masaru Sugawara
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2002-11-29 12:59:20 | Re: Auto Vacuum Daemon (again...) |
Previous Message | Manfred Koizar | 2002-11-29 11:23:26 | Re: nested transactions |