From 1047021c5155a32a801240ec2fba796fc2fb0314 Mon Sep 17 00:00:00 2001
From: "mbarnson%sisna.com" <>
Date: Tue, 5 Nov 2002 12:07:18 +0000
Subject: Added information about versioncache back in. See bug 140332
---
docs/xml/database.xml | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
(limited to 'docs/xml/database.xml')
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?
+
+ Modifying Your Running System
+
+ Bugzilla optimizes database lookups by storing all relatively
+ static information in the
+ versioncache file, located in the
+ data/
+ subdirectory under your installation directory.
+
+ If you make a change to the structural data in your database (the
+ versions table for example), or to the
+ constants
+
+ encoded in defparams.pl, you will need to remove
+ the cached content from the data directory (by doing a
+ rm data/versioncache
+
+ ), or your changes won't show up.
+
+ versioncache
+ 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.
+
+
MySQL Bugzilla Database Introduction
--
cgit v1.2.3-24-g4f1b