security policy aka fine-grained access control (was: lock agains

I see that Mr. Buchan answered his own question (use dbms_lock inside an insert trigger to wait until the processing is done.) But after reading your question I looked at security policies aka fine-grained access control (dbms_rls) and started wondering, how can the fine-grained access control apply to an insert?
>From my trials and from what the documentation says, a security policy will
add an extra condition to the end of your where clause. But it also gives you the option to apply the security policy to an insert statement. Has anyone ever done that? If so, how and why?

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jacques Kilchoer
  INET: Jacques.Kilchoer_at_quest.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).