From: bryce-mozilla%nextbus.com <>
Date: Sat, 12 Jun 1999 08:16:44 +0000 (+0000)
Subject: Give administrators a clue that upgrading is possible, even straightforward.
X-Git-Tag: bugzilla-2.6~40
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9b7fd7e1864b1d29949106bdbd5f200fe79eb646;p=thirdparty%2Fbugzilla.git

Give administrators a clue that upgrading is possible, even straightforward.
---

diff --git a/README b/README
index 4d9389aaef..1d4e9c88b5 100644
--- 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