No. I want to use bind variable instead of literals to eliminate trigger
codes are parsed over and over again.
Dave
>From: "Niall Litchfield" <niall.litchfield_at_gmail.com>
>To: davidb158_at_hotmail.com
>CC: oracle-l_at_freelists.org
>Subject: Re: bind variable
>Date: Mon, 6 Nov 2006 13:50:01 +0000
>
>Unless I'm missing something obvious you'd be wanting to use the
>:new.<columnname> and :old.<columnname> construct in your trigger.
>
>On 11/6/06, David Boyd <davidb158_at_hotmail.com> wrote:
>>
>>Hi All,
>>
>>We have lots of row level audit triggers that audit update and delete on
>>every column for each row. Our database is 9.2.0.6 and cursor_sharing
>>parameter is set to exact. Therefore the SQL statements in the trigger
>>that
>>differ in some literals are not shared. Let's say that we don't want
>>change
>>the cursor_sharing parameter and would like to use bind variable. But
>>bind
>>variable can not be used in the trigger. The alternative is to create a
>>procedure that uses bind variable and is called by the trigger. Does any
>>one have experience on this? How is the performance with calling the
>>procedure from trigger back and forth? The database is shared by many
>>home
>>grow and vendor applications. If we change the cursor_sharing to force,
>>what are the pros and cons?
Stay in touch with old friends and meet new ones with Windows Live Spaces
http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Nov 06 2006 - 10:44:17 CST
