Hello, A few weeks ago, I sent a notice about reverting the DB on the test server. In order to fix things up in one of our upgrade scripts (upgrade to 172), I will need to revert the DB on the test server back yet again. I will be reverting to the version of the DB I put on the test server on Feb 13th, so any data you have created on the test server since then will be lost. Once again, I apologize for any inconvenience this causes.
This does give me a good opportunity to mention that although we strive to keep the test server data in tact whenever possible, since the test server is running an unstable/unreleased version of Mifos that is in development, there are often cases where we need to revert or change data to handle any issues that have come up causing upgrade issues or data corruption. For this reason, it is best that any testing that you do which requires your data to stay in tact over time be done on a local build of Mifos on your own machine. Additionally, it is also important that you take regular backups of your own data on your local build if possible, so that you can reload or revert to an older DB whenever necessary so that you can apply any changes to upgrade scripts if applicable. In the current circumstances, we are changing the upgrade script to v172 of the DB so after that change is checked in, reloading a DB backup from prior to v172 and then deploying the latest WAR file will ensure your DB and data are in the most current/correct state. I will send an email once this change has been checked in so you can take these steps, if necessary. If you have any questions about any of the above information (as it applies to your own local build or the test server), please let me know. Thanks, Aliya ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
