Re: Analyze sql transaction before commited

I'm not familiar with a way of un-granting privileges to a user, so he
will not be able to use the "Union" sql command.
Is there a way of doing this?
Frank <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> Tzach wrote:
> 
> > Hello Sebastian,
> > 
> > I thank you for your prompt response.
> > My goal is to find if someone is trying to execute an SQL statement
> > that I do not approve. For instance I do not allow the following SQL
> > commands: DROP, TRUNCATE, UNION .... I want to be able to filter the
> > SQL transactions that have these words. I read something about "Two
> > Phase Commit" but this mechanisem pre-requisite is that the database
> > will be brought up in a special mode -that will probably hit
> > performance-. I'm loking for a better way.
> > 
> > Any suggestions?
> > 
> > Regards,
> > Tzach.
> > [EMAIL PROTECTED] (Sebastian DiFelice) wrote in message news:<[EMAIL PROTECTED]>...
> > 
> >>Please define 'legal', if you mean inserting rows with invalid
> >>constraints, Oracle will take care of this, if you are speaking of
> >>crappy data (incorrect addresses etc.) there is no easy way to do this
> >>without some performance degradation.
> >>
> >>Sebastian DiFelice
> >>
> >>[EMAIL PROTECTED] (Tzach) wrote in message news:<[EMAIL PROTECTED]>...
> >>
> >>>Hello,
> >>>
> >>>I am lloking for a way of analyzing an sql transaction before it is
> >>>commited.
> >>>Let say that I have 20 users, each one of them is using SQL*Plus to
> >>>perform DML actions.
> >>>I would like to make sure that none of them is performing illegal
> >>>operations by viewing the SQL transaction in the Oracle sever,
> >>>analyzing its content, and only if it is legal allow it to commit.
> >>>I'm looking into ways of interfacing with the databse processes (API
> >>>of some sort) rather then triggers and the like.
> >>>
> >>>Thank you for your help.
> 
> What about simply not granting these privileges to the users?