1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
5
>Modifying Your Running System</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10
TITLE="The Bugzilla Guide - 2.18.4 Release"
11
HREF="index.html"><LINK
13
TITLE="Customising Bugzilla"
14
HREF="customization.html"><LINK
16
TITLE="Customizing Who Can Change What"
17
HREF="cust-change-permissions.html"><LINK
19
TITLE="MySQL Bugzilla Database Introduction"
20
HREF="dbdoc.html"></HEAD
31
SUMMARY="Header navigation table"
40
>The Bugzilla Guide - 2.18.4 Release</TH
48
HREF="cust-change-permissions.html"
56
>Chapter 5. Customising Bugzilla</TD
77
>5.4. Modifying Your Running System</A
80
> Bugzilla optimizes database lookups by storing all relatively
81
static information in the <TT
85
file, located in the <TT
89
subdirectory under your installation directory.
92
> If you make a change to the structural data in your database (the
93
versions table for example), or to the <SPAN
100
>, you will need to remove
101
the cached content from the data directory (by doing a
104
>rm data/versioncache</B
105
>), or your changes won't show up.
111
> gets regenerated automatically
112
whenever it's more than an hour old, so Bugzilla will eventually
113
notice your changes by itself, but generally you want it to notice
114
right away, so that you can test things.
122
SUMMARY="Footer navigation table"
133
HREF="cust-change-permissions.html"
161
>Customizing Who Can Change What</TD
167
HREF="customization.html"
175
>MySQL Bugzilla Database Introduction</TD
b'\\ No newline at end of file'