It might not be a role from dba roles, but look at the underlying source
for the view, and you'll see that its EXPLICITY excluded in the where
clause, even though its ALL stored in USER$.
joe
"Maser, Donna (SEA)" wrote:
>
> Good point Joe. Happily, we are both right.
> Although you are correc
Good point Joe. Happily, we are both right.
Although you are correct that PUBLIC gets created
as a role 'under the covers', it is not listed as
a role (try 'SELECT * FROM DBA_ROLES'), nor is it
ever referred to as a role in the Oracle documentation.
If you RTFM (:> as you are so fond of
I beg to differ, look at sql.bsq,
quote:
create role public
/
its right after the create user sys
joe
"Maser, Donna (SEA)" wrote:
>
> Ron,
>
> PUBLIC is not actually a ROLE, it is a 'user group'.
> It always is available to ALL users in a database.
> If used in reference to a syno
I would add that it is different from other roles in that you cannot revoke
it from a user. Everybody has public role automatically. There may be
other idiosyncracies about PUBLIC as well.
HTH
Gerardo
-Original Message-
Sent: Thursday, March 08, 2001 3:05 PM
To: Multiple recipients of
Ron,
PUBLIC is not actually a ROLE, it is a 'user group'.
It always is available to ALL users in a database.
If used in reference to a synonym, privilege, role,
or subroutine (variable, constant, function, procedure)
of a package it means the synonym, privilege, role,
or subroutine is accessib
public, a role built when the create database statement is executed (its
in sql.bsq).
what else would u like to know about it?
joe
"Smith, Ron L." wrote:
>
> Can anyone point me to a paper or explanation of the Oracle role? called
> PUBLIC? How do you manage permissions for PUBLIC?
>
> Ron Sm
