On Thu, Mar 12, 2009 at 7:36 PM, Paul <[email protected]> wrote: > Now the question that brings me here : handling model migrations with Qi4j. > > I'm used to build apps with the classic RDBMS tooling. Using an ORM or not > I'm handling database schema _and_ data migration with the help of > Liquibase.
No idea what that is, but I know that schema evolution slows down "RERO"-mode a lot. > How do you Qi4j guys handle model change over time for "already in > production" applications ? Ok, we are not there yet. But basically the runtime will detect schema changes "per-object' (in reality per state of object) and when a mismatch between "running" and "stored" schema is detected, the UnitOfWork will look up a 'migration-path'-hook which you install. Exactly how this is going to look is still debatable, and we welcome any insights. The next step would be to enable the 'hooks' to be automatically created for common refactorings and changes to the code, such as simple renames, moves, deletes and additions, from within the IDEs refactoring system. Sounds too 'automagic'?? Yeah, maybe, it remains to be seen. Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
