Re: Granting users ability to create a view

Hi,Brian,

Maybe below procedures are useful

1. create user tableowner...;
2. grant connect(resource) to tableowner...
3. create user member...;
4. grant connect(resource) to member...;
5. create role r_privilege_table...;
6. connect to tableowner then

    create tableowner_table_a...;
    create tableowner_table_b...;
    grant all(select,insert,update,delete) on tableowner_table_a

             to r_privilege_table;
    grant all(select,insert,update,delete) on tableowner_table_b

            to r_privilege_table;
7. grant member to r_privilege_table...; (above detail command syntax pls refer ORACLE relevant handbook)

then this "member" user could read/write tableowner_table_a & tableowner_table_b;
same as "create view v_table as select * from tableowner_table_a(b)" privileges

Regards,
Lucy

HTC MIS staff
email:lucy_Jih_at_HTC.com.tw

Brian Lavender ¼¶¼g©ó¤å³¹ <7gl6q1$p21$1_at_nnrp1.dejanews.com>...
>I created a database with ten tables. I created a role where the role could
>insert, update, delete, and update. I then granted this role to selected
>users. When a user tries to create a view, it is rejected. I read that the
>USER must have the priveledge, not granted from a role. Am I missing
>something? I seems like a user with priveledges granted from a role ought
to
>be able to create a view.
>
>brian
>--
>Brian E. Lavender
>US Army Corps of Engineers -- Programmer / Systems Analyst
>Sacramento, CA (916) 557-6623
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Mon May 03 1999 - 23:37:52 CDT