db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject Re: Causing trigger to recompile during hard upgrade
Date Fri, 16 Apr 2010 20:25:25 GMT
Other option would be mark them as invalid so that when they are used
next time, they will be automatically recompiled.


On Fri, Apr 16, 2010 at 12:47 PM, Mamta Satoor <msatoor@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

View raw message