Re: Create object in other schemas?

From: DA Morgan <damorgan_at_psoug.org>
Date: Fri, 01 Dec 2006 08:37:48 -0800
Message-ID: <1164991067.195144@bubbleator.drizzle.com>

Heikki Siltala wrote:
>
> DA Morgan kirjoitti:

>> The first is that you could grant DROP ANY TABLE to User1 and then
>> write a DDL Event Trigger to RAISE an exception if the table's owner
>> isn't either A, B, or C. (same code in Morgan's Library at www.psoug.org
>> under DDL EVENT TRIGGER).

>
> We have been using this solution in a production enviroment for several
> years and it works OK.
>
> We have a consolidated Oracle database where each schema represents a
> dataset which means that each schema is "a logical subdatabase". On the
> other hand we have a rule that each user (read: person) accessing the
> database must be correclty identified so logging in using schema owner's
> username & password is strictly forbidden.
>
> The only way to implement this was to grant "subdatabase administrators"
> DROP ANY..., CREATE ANY..., ALTER ANY... rights and then build a control
> DDL trigger that controls on what schema(s) a user can execute DDL
> operations.

The concept of building a relational application in a relational database by adding a column to each table identifying the dataset is a non-starter? Why?

But why are people dropping production tables?

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

Received on Fri Dec 01 2006 - 10:37:48 CST