db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1402509 - /db/derby/docs/trunk/src/ref/rrefsyscsinvalidatestoredstmts.dita
Date Fri, 26 Oct 2012 13:40:15 GMT
Author: chaase3
Date: Fri Oct 26 13:40:14 2012
New Revision: 1402509

URL: http://svn.apache.org/viewvc?rev=1402509&view=rev
Log:
DERBY-5793  Document new SYSCS_INVALIDATE_STORED_STATEMENTS procedure

Modified the new Reference Manual topic.

Patch: DERBY-5793-3.diff

Modified:
    db/derby/docs/trunk/src/ref/rrefsyscsinvalidatestoredstmts.dita

Modified: db/derby/docs/trunk/src/ref/rrefsyscsinvalidatestoredstmts.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsyscsinvalidatestoredstmts.dita?rev=1402509&r1=1402508&r2=1402509&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsyscsinvalidatestoredstmts.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsyscsinvalidatestoredstmts.dita Fri Oct 26 13:40:14 2012
@@ -24,8 +24,17 @@ limitations under the License.
 system procedure invalidates all stored prepared statements (that is, all
 statements in the <xref href="rrefsistabs33768.dita#rrefsistabs33768"></xref>).
 The next time one of the invalid stored prepared statements is executed, it will
-be recompiled, and a new plan will be generated for it. This procedure can be
-especially useful after an upgrade.</p></section>
+be recompiled, and a new plan will be generated for it.</p>
+<p>Run <codeph>SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS</codeph> whenever
+you think that your metadata queries or triggers are misbehaving -- for example,
+if they throw <codeph>java.lang.NoSuchMethodError</codeph> or
+<codeph>java.lang.NoSuchMethodException</codeph> on execution.
+<ph conref="../conrefs.dita#prod/productshortname"></ph> stores plans for
+triggers and metadata queries in the database. These should be invalidated
+automatically on upgrade and at other necessary times. Should you encounter an
+instance where they are not, you have found a bug that you should report, but
+one that you can likely work around by running
+<codeph>SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS</codeph>.</p></section>
 <section><title>Syntax</title>
 <codeblock>SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS()</codeblock>
 <p>No result is returned by this procedure.</p></section>



Mime
View raw message