From 4fc22b4fc7de2653894e91d3945876e2b6d9cd72 Mon Sep 17 00:00:00 2001 From: "terry%netscape.com" Date: Mon, 21 Sep 1998 23:29:39 +0000 Subject: [PATCH] Patch by (mostly) Bert Driehuis -- explain a bit about the versioncache file. git-svn-id: svn://10.0.0.236/trunk@10634 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/webtools/bugzilla/README | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/mozilla/webtools/bugzilla/README b/mozilla/webtools/bugzilla/README index f7bc7ace564..dab08e205d5 100644 --- a/mozilla/webtools/bugzilla/README +++ b/mozilla/webtools/bugzilla/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.