Hi , many thanks. * this may make migration difficult or impossible. see http://article.gmane.org/gmane.comp.finance.mifos.devel/3409 We have the same findings as you, but it should be improved with new Hibernate versions , hopefully
* this doesn't obliviate the need for SQL standards like table/column naming conventions I am writing the document: we agree * this still may not directly address the root cause of the bug... depending on how a particular database instance is configured, dumping and importing may not function correctly In fact should be more like an export and import of data * this would likely be more work than other proposed implementations True, but could insure a Datbase portability (I know is not in the scope now) If you wish to discuss the proposed implementation design further, please do so on the mifos-developer mailing list. OK For future reference: The attached patch (IssueTracker 1513.gz from Wed Feb 13 15:51:00 +0000 2008) was not accepted. See the following post for more details: Best ------------------------------------------------------------------------- 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/
