summaryrefslogtreecommitdiffstats
path: root/docs/xml
diff options
context:
space:
mode:
authormbarnson%sisna.com <>2002-11-05 13:07:18 +0100
committermbarnson%sisna.com <>2002-11-05 13:07:18 +0100
commit1047021c5155a32a801240ec2fba796fc2fb0314 (patch)
tree9a3e4a56053cf9829dd0fce22771501e84f2662c /docs/xml
parent56c60d0255d90a0fd37dc6d9b98dd310f9913d5b (diff)
downloadbugzilla-1047021c5155a32a801240ec2fba796fc2fb0314.tar.gz
bugzilla-1047021c5155a32a801240ec2fba796fc2fb0314.tar.xz
Added information about versioncache back in.
See bug 140332
Diffstat (limited to 'docs/xml')
-rw-r--r--docs/xml/database.xml26
1 files changed, 26 insertions, 0 deletions
diff --git a/docs/xml/database.xml b/docs/xml/database.xml
index f0cda4589..ae1918207 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>