db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Katherine Marsden <kmarsdende...@sbcglobal.net>
Subject Re: invalidating stored prepared statements like triggers at an installation.
Date Wed, 18 Jan 2012 17:22:48 GMT
On 1/17/2012 11:41 AM, Mike Matrigali wrote:
> Is there any existing way in the software to invalidate all the existing
> stored prepared statements (like compiled triggers).  Either a command
> in sane or insane or with a property on boot?
> The code does this now automatically on any number change in any of the
> 4 digits of the release.  But for quickly diagnoising a problem that may
> just be in a stored compiled form it would be nice to be able to run
> a quick command or property to invalidate them all.
> /mikem
I don't know that is a practical on-site solution, but soft upgrade to 
10.8 and then reverting to the old version might be an option.  I agree 
it would be good to have a command for this.

View raw message