Revision: 1570
http://mrbs.svn.sourceforge.net/mrbs/?rev=1570&view=rev
Author: cimorrison
Date: 2010-11-02 14:51:00 +0000 (Tue, 02 Nov 2010)
Log Message:
-----------
Updated the UPGRADE information
Modified Paths:
--------------
mrbs/branches/provisional_bookings_new_style/UPGRADE
Modified: mrbs/branches/provisional_bookings_new_style/UPGRADE
===================================================================
--- mrbs/branches/provisional_bookings_new_style/UPGRADE 2010-11-02
14:39:39 UTC (rev 1569)
+++ mrbs/branches/provisional_bookings_new_style/UPGRADE 2010-11-02
14:51:00 UTC (rev 1570)
@@ -9,42 +9,47 @@
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.
+MRBS database upgrades are in general 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.
+There are however some exceptions to this backward compatiblity, namely at
+the following transitions:
-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.
+MRBS 1.4.4.1 -> 1.4.5
-Upgrading from prior to mrbs 1.0-pre1
-======================================
+In these cases you will not be able to run the old version of MRBS against
+the upgraded database. You may therefore choose to make a copy of the
+database for test purposes and check that the upgrade process works before
+performing the upgrade on your production database.
-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
-level of backslash-escaping on room, area, and entry names and
-descriptions. This applied to certain characters such as single quote
-mark(') and backslash(\). As of version 1.0-pre1, these characters are
-handled correctly. If you see extra backslashes when MRBS displays names or
-descriptions, it is because these are in actually your database. You can
-edit the entries in MRBS or directly with your database SQL tool, or just
-ignore them.
-Upgrading from prior to mrbs 1.0 final
-======================================
+Upgrading from prior MRBS 1.4.5
+===============================
+MRBS 1.4.5 introduces the concept of tentative bookings, or bookings that
+require confirmation. To avoid confusion, what were previously known as
+"provisional bookings" have now been renamed "bookings requiring approval"
+and the config variable $provisional_enabled has been renamed
+$approval_enabled. You should update your config file accordingly.
-Please apply the upgrade2.my.sql (if using MySQL) or the
-the upgrade2.pg.sql (if using PostgreSQL) script, which
-adds a new column to the 'mrbs_repeat' table to support
-"n-weekly" repeats.
+Please also see the note about database compatibility above.
-Upgrading from prior mrbs 1.2-pre2
+
+Upgrading from prior MRBS 1.2-pre3
==================================
+mrbs 1.2-pre3 introduced area and room administrator email fields.
+
+Please apply the upgrade3.my.sql to add these fields. This file should work
+both with mysql and pgsql.
+
+
+Upgrading from prior MRBS 1.2-pre2
+==================================
+
Upgrading mysql database from previous charsets to Unicode :
You can use convert_db_to_utf8.php script to convert text in the
@@ -56,12 +61,34 @@
Running it more than once will make a right mess of any non-ASCII
text in the database.
-Upgrading from prior mrbs 1.2-pre3
-==================================
+
+Upgrading from prior to MRBS 1.0 final
+======================================
-mrbs 1.2-pre3 introduced area and room administrator email fields.
+Please apply the upgrade2.my.sql (if using MySQL) or the
+the upgrade2.pg.sql (if using PostgreSQL) script, which
+adds a new column to the 'mrbs_repeat' table to support
+"n-weekly" repeats.
-Please apply the upgrade3.my.sql to add these fields. This file should work
-both with mysql and pgsql.
+
+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
+level of backslash-escaping on room, area, and entry names and
+descriptions. This applied to certain characters such as single quote
+mark(') and backslash(\). As of version 1.0-pre1, these characters are
+handled correctly. If you see extra backslashes when MRBS displays names or
+descriptions, it is because these are in actually your database. You can
+edit the entries in MRBS or directly with your database SQL tool, or just
+ignore them.
+
+
+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.
+
$Id$
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Mrbs-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mrbs-commits
