Hi,
Security risk: it depends on what privileges these two users must have on different objects. There is no difference whether the privileges will be granted on the object itself or on its public synonym, if I'm not wrong.
Different approach: you may grant select privilege on any table (current and future) in the database using the following statement (execute it as sysdba):
grant select on any table to user2;
It is your decision what to use.
Regards, Geo
Main Topics
Browse All Topics





by: sathya_sPosted on 2006-07-19 at 05:09:02ID: 17137546
It would be bad. Developers can use "alter session set ATION" in their apps if they find it too onerous to
current_schema=THAT_APPLIC
prefix the schema name on tables.
There will be a possibility of Name space clash -- both will have
a same table "TEST" or something and won't be able to coexist. You should use a bare
minimum number of public synonyms.
Regards,
Sathya