On Thu, 2008-02-14 at 08:57 +0000, Roberto Musso wrote: >> 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
Agreed, and good thinking. A great place to capture this and brainstorm other ideas for architectural improvements is on mifos.org. It seems appropriate to add it here: http://mifos.org/developers/wiki/UpgradeHibernate Or perhaps as another child of this wiki page: http://mifos.org/developers/wiki/TechToDos It could be called, for instance, "Hibernate Automatic DDL" and might include some ideas about how migrations (to newer database versions) would work. >> 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 I think what you're saying is that it would be nice to have Mifos export/import functionality for all data and settings, right? If so, I agree. We can start another mailing list thread and/or page on mifos.org about that. >> 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) Agreed. And here are responses for your other related email: On Thu, Feb 14, 2008 at 06:23 -0800, Roberto Musso wrote: > I did some testing. > > I create some table on a Windows MySQL Database and I did a Dump: the > name of the table were transformed all in lower case. At this making a > restore on a Linux ssytem were created correctly with lower case name > and Hibernate was not anymore working. > > It seems that the ONLY naming convention that allows porting is to > have Dtabase Names and Table Names in lower case as MySql doc say: > > "To avoid problems caused by such differences (case isssue), it is > best to adopt a consistent convention, such as always creating and > referring to databases and tables using lowercase names. This > convention is recommended for maximum portability and ease of use." Good find. Here's a link, in case anyone else is curious: http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html > Without using lower_case_table_names or naming convention with > database names and table names lower case, the portability of the > database between Linux/Window and Mac involve to change again the code > in the dumped sql code. Standardizing on lower case sounds quite reasonable. I'll send a notice in another posting. -- Adam Monsen ------------------------------------------------------------------------- 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/
