From: Mike Krolewski <mkrolewski@rii.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Truncate table and Triggers
Date: Mon, 01 Jan 2001 21:38:56 GMT
Organization: Deja.com
Lines: 36
Message-ID: <92qtdf$i2o$1@nnrp1.deja.com>
References: <92qrjs$aku$07$1@news.t-online.com>
NNTP-Posting-Host: 140.142.183.60
X-Article-Creation-Date: Mon Jan 01 21:38:56 2001 GMT
X-Http-User-Agent: Mozilla/4.7 [en] (WinNT; U)
X-Http-Proxy: 1.0 x53.deja.com:80 (Squid/1.1.22) for client 140.142.183.60
X-MyDeja-Info: XMYDJUIDmikkrolewski


In article <92qrjs$aku$07$1@news.t-online.com>,
  "Nicolas Bronke" <newsgroup@trinity.de> wrote:
> I placed a delete trigger on a table to unpermit delete operations
 under a
> special condition.
>
> Now I fpund out, that truncate table ommit this rules. Everything is
 erased
> nevertheless from the rules.
>
> Perhaps it is logically, but how can I avoid this situation?
>
> regards
> Nicolas
>
>

Truncate command should fall into a privilege command. Assuming not
everyone is loging in as the owner of the table, one can restrict
issuing of the command.

Make a second user who has at least select access to the other user's
tables. Look into grants and synomyms. If the second user is going to
make inserts and updates, you add this to the grants. Your triggers
written for the owner of the tables will function with this scheme.


--
Michael Krolewski
Rosetta Inpharmatics
mkrolewski@rii.com
              Usual disclaimers


Sent via Deja.com
http://www.deja.com/