Revision: 1333
http://mrbs.svn.sourceforge.net/mrbs/?rev=1333&view=rev
Author: cimorrison
Date: 2010-04-21 08:46:28 +0000 (Wed, 21 Apr 2010)
Log Message:
-----------
Updated the Install and Upgrade instructions.
Modified Paths:
--------------
mrbs/trunk/INSTALL
mrbs/trunk/UPGRADE
Modified: mrbs/trunk/INSTALL
===================================================================
--- mrbs/trunk/INSTALL 2010-04-20 21:38:16 UTC (rev 1332)
+++ mrbs/trunk/INSTALL 2010-04-21 08:46:28 UTC (rev 1333)
@@ -93,19 +93,11 @@
For an upgrade:
-If you are upgrading from MRBS version 0.7 or later, and continuing to
-use MySQL, your database will be upgraded automatically if necessary
-when you first run MRBS. You will be prompted for a database (not MRBS)
-username and password with rights to create and alter tables.
+If you are upgrading from MRBS 1.2-pre3 or later, your database will be
+upgraded automatically if necessary when you first run MRBS. You will
+be prompted for a database (not MRBS) username and password with rights
+to create and alter tables. Otherwise, please se the UPGRADE file.
-The database format changed slightly between 0.6 and 0.7. To change the
-format of your data do:
-
-[MySQL] $ mysql mrbs < upgrade.my.sql
-
-(This does not apply to PostgreSQL, which was not supported then.)
-Also see the file UPGRADE in the distribution.
-
For a second installation or to use different table names:
If you have table name conflicts or want to do a second installation
Modified: mrbs/trunk/UPGRADE
===================================================================
--- mrbs/trunk/UPGRADE 2010-04-20 21:38:16 UTC (rev 1332)
+++ mrbs/trunk/UPGRADE 2010-04-21 08:46:28 UTC (rev 1333)
@@ -1,12 +1,28 @@
Upgrade Information for previous releases of MRBS:
--------------------------------------------------
+If you are upgrading from MRBS 1.2-pre3 or later, then MRBS will
+automatically execute any necessary database upgrades when it is first
+run. It will prompt you for a database (not MRBS) username and password
+with rights to create and alter tables.
+
+It would be a sensible precaution to take a backup of your database before
+the upgrade.
+
+MRBS database upgrades are intended to be backwards compatible, so that you
+should still be able to run the old version of MRBS against the new database
+schema. This will allow you to install the new version of MRBS in a separate
+directory while you configure and test it. When you are happy with the
+new release you can switch the directory to be your production directory.
+
+
+Upgrading from prior to mrbs 0.7
+================================
There was a change to the database schema at version 0.7. See the
information in INSTALL on using the upgrade.my.sql script.
-There have been no database changes from version 0.7, so your current
-database should work just fine. Although, naturally, you should back up
-any data you have before using a new version.
+Upgrading from prior to mrbs 1.0-pre1
+======================================
A change in version 1.0-pre1 might affect the appearance of entries in your
existing database. Prior versions of MRBS did an extra and unnecessary
@@ -22,7 +38,7 @@
======================================
Please apply the upgrade2.my.sql (if using MySQL) or the
-the upgrade2.my.sql (if using PostgreSQL) script, which
+the upgrade2.pg.sql (if using PostgreSQL) script, which
adds a new column to the 'mrbs_repeat' table to support
"n-weekly" repeats.
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
_______________________________________________
Mrbs-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mrbs-commits
