On Mon, Jan 06, 2003 at 12:45:25 +0200,
Tambet Matiisen <[EMAIL PROTECTED]> wrote:
> btw, views "execute" also with owner's rights, ie if you grant select on view, you
>do not have to grant select on every table used in view. Still current_user in view
>returns "caller", while maybe it should r
In PostgreSQL 7.3 you have option to execute function with owner's rights or caller's
rights. Default is caller's rights (as it was before 7.3), you probably want owner's
rights. See development version of docs:
http://developer.postgresql.org/docs/postgres/sql-createfunction.html
btw, views "
Hello,
PostgreSQL 7.3 happily introduced permissions on functions. Now, having
granted execution to a given function to a given user, I find myself with
"access denied" errors on the objects that the function actually uses (e.g.
a table on which it makes a select). So:
1. Am I missing something a
Hi, All!
IMHO it will be useful to have EXECUTE privilege on procedures. It may be
realized through GRANT SELECT ON [procedure] since we cannot directly
execute procedure in SQL. But anyway ability to restrict access to
procedures seems good thing.
What do you think about it?
Dmitry
-
