From 2545c0950c4f0fde8f78b265217fa9f523eff7bf Mon Sep 17 00:00:00 2001 From: "lpsolit%gmail.com" <> Date: Tue, 20 Jun 2006 03:15:17 +0000 Subject: Bug 304601: Bugzilla::Config's :locations exports need to be in their own module - Patch by Frédéric Buclin r=mkanat for the main patch, r=myk for the patch about CGI.pm a=justdave MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bug 328637: Remove all legal_* versioncache arrays - Patch by Frédéric Buclin r=mkanat a=justdave Bug 110503 - Eliminate versioncache --- docs/xml/customization.xml | 26 -------------------------- 1 file changed, 26 deletions(-) (limited to 'docs') diff --git a/docs/xml/customization.xml b/docs/xml/customization.xml index f7a08da0d..aefacda67 100644 --- a/docs/xml/customization.xml +++ b/docs/xml/customization.xml @@ -753,32 +753,6 @@ ask in the newsgroup. - -
- 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 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. - -
MySQL Bugzilla Database Introduction -- cgit v1.2.3-24-g4f1b