]> git.ipfire.org Git - thirdparty/bugzilla.git/commitdiff
Give administrators a clue that upgrading is possible, even straightforward.
authorbryce-mozilla%nextbus.com <>
Sat, 12 Jun 1999 08:16:44 +0000 (08:16 +0000)
committerbryce-mozilla%nextbus.com <>
Sat, 12 Jun 1999 08:16:44 +0000 (08:16 +0000)
README

diff --git a/README b/README
index 4d9389aaef335488cc59d3af19465bac7560d20d..1d4e9c88b58fa0dcd27396951e9e88a14da78049 100644 (file)
--- a/README
+++ b/README
@@ -469,7 +469,17 @@ generally you want it to notice right away, so that you can test things.
 
 Appendix C. Upgrading from previous versions of BugZilla
 
-[This section under construction].
+The developers of BugZilla are constantly adding new tables, columns and fields.
+You'll get SQL errors if you just update the code.  The strategy to update is
+to read the CHANGES file backwards, and apply all of the instructions given,
+typically things like:
+
+       ./makeattachmenttable.sh
+       ./makegroupstable.sh
+       alter table products add column disallownew tinyint not null;
+
+Someday someone should write a script that queries the existing database
+for all the required columns, and if any are missing, adds them.
 
 
 Appendix D. History