Re: sequence auditting

From: Scott Urman <surman_at_oracle.com>
Date: 1995/10/09
Message-ID: <45bmnj$bvt_at_inet-nntp-gw-1.us.oracle.com>#1/1


In article <45bkqm$2po_at_post.gsfc.nasa.gov>, joanne_at_daac.gsfc.nasa.gov (Joanne Woytek) writes:
|> Is there any way, either through auditting and/or triggers, to catch
|> whenever a certain sequence is updatted; i.e. whenever someone issues
|> a xxxx.NewVal?
|>
|>
|> Thanks
|>
|>
|> Joanne Woytek
|> joanne_at_daac.gsfc.nasa.gov
|> Code 902.2
|> NASA/GSFC

Hm. I don't think you can do this with sequences directly, but you could write

an access procedure to do it.  Create the sequence in a priviledged account,
and don't grant select on it.  In this same account, create a procedure which
will return sequence.nextval.  This procedure can do whatever auditing is
required. You then grant execute on the procedure to those who need it. (Actually, a function would probably make more sense than a procedure - since it will only return one value. If you're on 7.1, it could even be used in a SQL statement just like seq.nextval.) Received on Mon Oct 09 1995 - 00:00:00 CET

Original text of this message