Re: Make table read-only

"Michel Cadot" <micadot{at}altern{dot}org> wrote:

[snip]
> Just one precision on what i thought about triggers.
> I didn't say to use them for auditing purpose

[neither did I, I hope]

> but to avoid the statement,
> that is use raise_application_error to abort the statement.
> But i agree with you: all that (and the read only view from Daniel) don't
> make a real read-only table but something like a workaround.

A very good definition.  

> Btw, "audit trigger" audits drop trigger (as well as create trigger, alter
> trigger, alter table enable/disable all triggers).

True. I realised that. But it audits it, usually, into AUD$. Which is at the mercy of the DBA's good intentions. And auditing can be turned off -which, of course, is itself audited (because it would require an instance bounce... hello Alert Log!). But again: knowing it was done is too late for the high-security crowd.

But we agree. I like the "workaround" definition.

Regards
HJR Received on Wed Oct 20 2004 - 16:11:56 CDT