Changes between Version 2 and Version 3 of MapGuideRfc23
- Timestamp:
- 07/05/07 09:31:43 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc23
v2 v3 33 33 There was some report from the user group that the !MapGuide repository got corrupted (though recoverable). The Berkeley DB XML 2.3 upgrade could help minimize such incident. 34 34 35 The benefits of Berkeley DB XML 2.3 release include :35 The benefits of Berkeley DB XML 2.3 release include conformance to W3C recommendations for XQuery 1.0 and XPath 2.0, bug fixes, and performance improvements: 36 36 37 * General bug fixes. 38 * Conformance to W3C recommendations for XQuery 1.0 and XPath 2.0. 39 * Performance and scalability improvements. 37 http://www.oracle.com/technology/documentation/berkeley-db/xml/change-log.html 40 38 41 39 == Proposed Solution == … … 44 42 45 43 * The server will detect a version mismatch at startup and throw an exception, prompting the user to upgrade. 46 * The installer will back up the existing repositories, then run the upgrade script.47 * The installer will need to install the upgrade script so that itcan be run independently.44 * The installer will back up the existing repositories, then run the upgrade utilities. 45 * The installer will need to install the upgrade utilities so that they can be run independently. 48 46 49 47 == Implications == 50 48 51 There is no way to revert the upgrade, so the repositories must be backed up. 49 * The database format has been changed and there is no way to revert the upgrade, so the repositories must be backed up. 50 * There have been 5 patches for Berkeley DB XML 2.3 release which will be included with the upgrade: 52 51 53 Users must read documentation on repository upgrade before performing an upgrade, or there is risk of data loss. 54 52 http://www.oracle.com/technology/products/berkeley-db/xml/update/2.3.10/patch.2.3.10.html 53 55 54 == Test Plan == 56 55