Re: Limit UPDATE statements to affect only one row

Thanks for the prompt response!

sybrandb wrote:
> Note: Sooner or later no one will understand what is happening.
>

This is correct, the business logic for such madness is: A column on a public table is driving the visibility of data in other tables protected by VPD and OLS, to make the protected data available all users and groups (business requirement) I written a procedure (MAKE_PUBLIC) to do this.

My development team decided to use Hibernate (against my advice) rather than using JDBC or Toplink for their mid tier DAO which make the use of stored procedures very difficult for them. Also they have a time constraint, bla bla excuses excuses. Being the helpful DBA I want to be I thought there might be a solution to make their lives easier by allowing them to control the visibility of the protected data using an update. I also use application context to make sure the user has the required LDAP entries before allowing the update.

For a security measure I want to prevent bulk updates on the column and have a trigger on the table to call my stored procedure. This would be the same as calling the MAKE_PUBLIC stored procedure but through normal DML instead.

Anyway, I will investigate the instead of triggers quickly and keep you posted.

Regards
Bernard Received on Fri Aug 11 2006 - 06:51:20 CDT