You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Mamta Satoor <ms...@gmail.com> on 2010/04/16 21:47:22 UTC
Causing trigger to recompile during hard upgrade
Hi,
I was wondering if anyone had any knowledge on how one can force the
triggers to be recompiled during the hard upgrade. For DERBY-1482, I
need additional information to be collected for triggers than what we
did in 10.5 or earlier releases. In case of databases created prior to
10.6, during hard upgrade, i would like us to recompile(or drop and
recreate) the existing triggers so new information can be collected
for them. If anyone knows of any such way, I will highly appreciate
that.
thanks,
Mamta
Re: Causing trigger to recompile during hard upgrade
Posted by Mamta Satoor <ms...@gmail.com>.
Thanks, Kathey. I was starting to look at invalidating all the
triggers at hard upgrade time but let me first look at the code you
mentioned.
Mamta
On Fri, Apr 16, 2010 at 2:31 PM, Kathey Marsden
<km...@sbcglobal.net> wrote:
> On 4/16/2010 1:25 PM, Mamta Satoor wrote:
>>
>> Other option would be mark them as invalid so that when they are used
>> next time, they will be automatically recompiled.
>>
>>
>
> I have not been following this thread, so may be misinterpreting the
> question, but I think any stored plan gets recompiled on any version change
> in DD_Version handleMinorRevisionChange.
>
>
>
Re: Causing trigger to recompile during hard upgrade
Posted by Kathey Marsden <km...@sbcglobal.net>.
On 4/16/2010 1:25 PM, Mamta Satoor wrote:
> Other option would be mark them as invalid so that when they are used
> next time, they will be automatically recompiled.
>
>
I have not been following this thread, so may be misinterpreting the
question, but I think any stored plan gets recompiled on any version
change in DD_Version handleMinorRevisionChange.
Re: Causing trigger to recompile during hard upgrade
Posted by Mamta Satoor <ms...@gmail.com>.
Other option would be mark them as invalid so that when they are used
next time, they will be automatically recompiled.
Mamta
On Fri, Apr 16, 2010 at 12:47 PM, Mamta Satoor <ms...@gmail.com> wrote:
> Hi,
>
> I was wondering if anyone had any knowledge on how one can force the
> triggers to be recompiled during the hard upgrade. For DERBY-1482, I
> need additional information to be collected for triggers than what we
> did in 10.5 or earlier releases. In case of databases created prior to
> 10.6, during hard upgrade, i would like us to recompile(or drop and
> recreate) the existing triggers so new information can be collected
> for them. If anyone knows of any such way, I will highly appreciate
> that.
>
> thanks,
> Mamta
>