= !MapGuide RFC 23 - Berkeley DB XML 2.3 Upgrade =

This page contains a change request (RFC) for the !MapGuide Open Source project.  
More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.


== Status == 
 
||RFC Template Version||(1.0)|| 
||Submission Date||July 3, 2007||
||Last Modified||Steve Dang [[Timestamp]]||
||Author||Steve Dang||
||RFC Status||Not ready for review||
||Implementation Status||pending||
||Proposed Milestone||1.3||
||Assigned PSC guide(s)||||
||'''Voting History'''||||
||+1||||
||+0||||
||-0||||
||-1||||
 
== Overview ==

This RFC updates !MapGuide to use the latest version of Berkeley DB XML.

For details, refer to Berkeley DB XML 2.3 release notes: 

 http://www.oracle.com/technology/documentation/berkeley-db/xml/relnotes.html

== Motivation ==

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.

The benefits of Berkeley DB XML 2.3 release include: 

 * General bug fixes.
 * Conformance to W3C recommendations for XQuery 1.0 and XPath 2.0.
 * Performance and scalability improvements.

== Proposed Solution ==

Modifications need to be made to the !MapGuide server and its installer:

 * The server will detect a version mismatch at startup and throw an exception, prompting the user to upgrade.
 * The installer will back up the existing repositories, then run the upgrade script.
 * The installer will need to install the upgrade script so that it can be run independently.

== Implications ==

There is no way to revert the upgrade, so the repositories must be backed up.

Users must read documentation on repository upgrade before performing an upgrade, or there is risk of data loss.

== Test Plan ==

Tests need to be done after the upgrade:

 * Resource Service unit tests must all pass.
 * Scripts that back up, restore, and recover repositories must run successfully.

== Funding/Resources ==

Supplied by Autodesk.