In learning how Mayfly is used in Mifos I came across an existing Mifos bug and a potential solution.
Summary: We can add a unique index to PERSONNEL.LOGIN_NAME if Mayfly is upgraded to a jar built from the latest CVS HEAD revision. The bug: https://mifos.dev.java.net/issues/show_bug.cgi?id=1387 The potential solution: http://sourceforge.net/mailarchive/message.php?msg_name=200711300016.lAU0G9304207%40panix5.panix.com (same url, snipped: http://tinyurl.com/2skxu5) Additional comments: Mifos unit tests may eventually be refactored to do less with Mayfly and more with mock objects. For now, it would be nice to have support in the current architecture for upgrading SQL databases by adding/removing indexes as necessary. It would have to be confirmed that all existing Mayfly and Mifos unit tests pass using the fresh Mayfly jar, but I can't think of any reason why they wouldn't. It is also possible that Mayfly features could change before the next release, but Mayfly itself is in "Alpha" anyway (not that it makes any difference... the software seems stable enough even at CVS HEAD -- all Mayfly unit tests passed last time I tried them). Thoughts? -- Adam Monsen ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
