Check into the RDBMS feature of "row-level security" (a.k.a. PL/SQL supplied
package DBMS_RLS, a.k.a. "virtual private database"), which is an integral
part of the "multi-org" functionality in Oracle Apps R11i. It's perfectly
suited for your requirements...
I've a paper and a quickie little demo
Couldn't you do this with a view
something like
create view trans_view
as
select *
from (select t.*
from transaction_all t,
user_roles u
where granted_role = 'POWER_USER'
union
select t2.*
from transactions)
-Original Message-
Sent: Monday,
Dennis:
The goal of the partitioning/archive are: better performance, faster and
fewer full-table scans, faster RMAN backups (move history to read-only
tablespaces), indexing history differently than active data to speed
research and to generally reduce the frequency of the "the database is
runni
Stephen
I missed one example...
Developer Connects
SELECT * FROM transaction; -- hits the transaction
table
I had thought of public synonym for user, private synonym for application.
But then I would have to create private synonyms for each developer.
I know, I know. The d
Kevin
I have always heard private synonyms are the preferred way to accomplish
what you want. If you prefer, you could assign developers the private
synonyms instead and everyone else gets the public one that gives access to
the entire table.
Looking at the larger issue, what is your goal wi
Create the program to access the transaction table within its schema
directly and use a public synonym for power users. That should work.
If the transaction table is owned by another user, create a single synonym
within the program schema and a public synonym thereafter.
Thank You
Stephen P. K
