From: mbarnson%sisna.com <>
Date: Tue, 5 Nov 2002 12:07:18 +0000 (+0000)
Subject: Added information about versioncache back in.
X-Git-Tag: bugzilla-2.17.1~18
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1047021c5155a32a801240ec2fba796fc2fb0314;p=thirdparty%2Fbugzilla.git

Added information about versioncache back in.
See bug 140332
---

diff --git a/docs/sgml/database.sgml b/docs/sgml/database.sgml
index f0cda45893..ae1918207c 100644
--- a/docs/sgml/database.sgml
+++ b/docs/sgml/database.sgml
@@ -8,6 +8,32 @@
     tables to document dependencies. Any takers?</para>
   </note>
 
+  <section id="dbmodify">
+      <title>Modifying Your Running System</title>
+
+      <para>Bugzilla optimizes database lookups by storing all relatively
+      static information in the 
+      <filename>versioncache</filename> file, located in the 
+      <filename class="directory">data/</filename>
+      subdirectory under your installation directory.</para>
+
+      <para>If you make a change to the structural data in your database (the
+      versions table for example), or to the 
+      <quote>constants</quote>
+
+      encoded in <filename>defparams.pl</filename>, you will need to remove 
+      the cached content from the data directory (by doing a 
+      <quote>rm data/versioncache</quote>
+
+      ), or your changes won't show up.</para>
+
+      <para> <filename>versioncache</filename> 
+      gets automatically regenerated whenever it's more than
+      an hour old, so Bugzilla will eventually notice your changes by itself,
+      but generally you want it to notice right away, so that you can test
+      things.</para>
+    </section>
+
   <section id="dbdoc">
     <title>MySQL Bugzilla Database Introduction</title>
 
diff --git a/docs/xml/database.xml b/docs/xml/database.xml
index f0cda45893..ae1918207c 100644
--- a/docs/xml/database.xml
+++ b/docs/xml/database.xml
@@ -8,6 +8,32 @@
     tables to document dependencies. Any takers?</para>
   </note>
 
+  <section id="dbmodify">
+      <title>Modifying Your Running System</title>
+
+      <para>Bugzilla optimizes database lookups by storing all relatively
+      static information in the 
+      <filename>versioncache</filename> file, located in the 
+      <filename class="directory">data/</filename>
+      subdirectory under your installation directory.</para>
+
+      <para>If you make a change to the structural data in your database (the
+      versions table for example), or to the 
+      <quote>constants</quote>
+
+      encoded in <filename>defparams.pl</filename>, you will need to remove 
+      the cached content from the data directory (by doing a 
+      <quote>rm data/versioncache</quote>
+
+      ), or your changes won't show up.</para>
+
+      <para> <filename>versioncache</filename> 
+      gets automatically regenerated whenever it's more than
+      an hour old, so Bugzilla will eventually notice your changes by itself,
+      but generally you want it to notice right away, so that you can test
+      things.</para>
+    </section>
+
   <section id="dbdoc">
     <title>MySQL Bugzilla Database Introduction</title>