summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/en/xml/customization.xml26
1 files changed, 0 insertions, 26 deletions
diff --git a/docs/en/xml/customization.xml b/docs/en/xml/customization.xml
index f7a08da0d..aefacda67 100644
--- a/docs/en/xml/customization.xml
+++ b/docs/en/xml/customization.xml
@@ -753,32 +753,6 @@
ask in the newsgroup.
</para>
</section>
-
- <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
- <command>rm data/versioncache</command>), or your changes won't show up.
- </para>
-
- <para>
- <filename>versioncache</filename> gets regenerated automatically
- 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>