From f0324c374c51b61a8615044631337a60eb9a37a8 Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" <> Date: Fri, 3 Jan 2003 01:29:23 +0000 Subject: Recomiple the docs for the 2.17.3 release --- docs/html/dbmodify.html | 184 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 184 insertions(+) create mode 100644 docs/html/dbmodify.html (limited to 'docs/html/dbmodify.html') diff --git a/docs/html/dbmodify.html b/docs/html/dbmodify.html new file mode 100644 index 000000000..6b7d3ea5d --- /dev/null +++ b/docs/html/dbmodify.html @@ -0,0 +1,184 @@ +Modifying Your Running System
The Bugzilla Guide
PrevAppendix B. The Bugzilla DatabaseNext

B.1. 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.


PrevHomeNext
The Bugzilla DatabaseUpMySQL Bugzilla Database Introduction
\ No newline at end of file -- cgit v1.2.3-24-g4f1b