summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorterry%netscape.com <>1998-09-22 08:29:39 +0200
committerterry%netscape.com <>1998-09-22 08:29:39 +0200
commit1d349dc730fa0514dbf0c04c7c4352a99fecd95d (patch)
treed980c269da943102810a558442784cc0231e42b4
parent17f74f22eab906e3454429734aae4c01cc554d19 (diff)
downloadbugzilla-1d349dc730fa0514dbf0c04c7c4352a99fecd95d.tar.gz
bugzilla-1d349dc730fa0514dbf0c04c7c4352a99fecd95d.tar.xz
Patch by (mostly) Bert Driehuis <bert_driehuis@nl.compuware.com> --
explain a bit about the versioncache file.
-rw-r--r--README19
1 files changed, 19 insertions, 0 deletions
diff --git a/README b/README
index f7bc7ace5..dab08e205 100644
--- a/README
+++ b/README
@@ -107,3 +107,22 @@ It's a good idea to set up a daily cronjob that does
This causes email that gets sent to anyone who has a NEW bug that
hasn't been touched for several days. For more info, see the
whinedays and whinemail parameters.
+
+
+6. 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 (we said before it
+needs to be writable, right?!)
+
+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!
+
+That file 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.