Concerning point #2, apparently we had problems a while ago with a particular data set, sometime last November I believe.
Unfortunately, an issue wasn't raised in the issue tracker at that time, so we don't know right now if it might or might not be an issue with the current version of Mifos. We will ask Mark next week (when he's back from his holidays) to try and reproduce the issue with the current version of Mifos, as he was the one that encountered the problem. Cheers Chico "Van Mittal-Henkle" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 02/27/2008 06:29 PM Please respond to Developer <[email protected]> To "Developer" <[email protected]> cc Subject Re: [Mifos-developer] Upgrades, Downgrades, What are they for? Chico, Thanks for your input. We should certainly have some continued discussion about this issue. With respect to point #2. So far I have not been aware of problems with the upgrade mechanism itself (the hooks for running SQL or java to upgrade the db schema and data). The problems thus far have had to do with incorrect or incomplete SQL code which would be an issue independent of the particular upgrade mechanism being used. Cheers, --Van From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chico Charlesworth Sent: Wednesday, February 27, 2008 1:24 AM To: Developer Subject: Re: [Mifos-developer] Upgrades, Downgrades, What are they for? A few things I would like to add concerning this: 1. IMHO, schema and data migration should not be tied directly to the application code. Ideally this should be managed outside the application scope, and a DBA should be responsible for this. 2. I haven't much confidence that the current mechanism will handle data migration correctly, indeed as I understand it we have had problems here when trying to upgrade. 3. At this time, I wouldn't recommend using this approach in a production environment as it would be too risky. Cheers Chico "Aliya Walji" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 02/27/2008 04:29 AM Please respond to Developer <[email protected]> To "Developer" <[email protected]> cc Subject Re: [Mifos-developer] Upgrades, Downgrades, What are they for? > Aside from the production environment, the automated upgrades are very > convenient for developer, demonstration and test deployments where > moving quickly and easily from one database version to the next is very > useful and time saving. I would argue that there may be some value from a production scenario perspective also. Yes, in the case where you have an experienced Sys Admin/DBA managing the upgrade of Mifos, they may want the control of not running the upgrades automatically. However, our software also needs to be supportable by users with less technical expertise and automatic upgrades may be useful for this type of user. I haven't thought through that completely, but I think it's a consideration in terms of whether we choose to have these in production or not. I definitely agree with Van for the developer/test scenarios. Absolutely necessary for those purposes :) 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/ ------------------------------------------------------------------------- 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/
------------------------------------------------------------------------- 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/
