From ec7719fef677376ab19b6ce2c126d05fffb66b45 Mon Sep 17 00:00:00 2001 From: "bryce-mozilla%nextbus.com" Date: Sat, 12 Jun 1999 01:16:44 +0000 Subject: [PATCH] Give administrators a clue that upgrading is possible, even straightforward. git-svn-id: svn://10.0.0.236/trunk@34950 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/webtools/bugzilla/README | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/mozilla/webtools/bugzilla/README b/mozilla/webtools/bugzilla/README index 4d9389aaef3..1d4e9c88b58 100644 --- a/mozilla/webtools/bugzilla/README +++ b/mozilla/webtools/bugzilla/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