Niclas, Rickard, First, thanks for your answers.
> > 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. Right, but on the other end, I think that schema evolution is a must have for RERO. Liquibase is a simple database changelog system allowing you to apply schema and data migrations easily and so makes handling schema evolution quicker in RERO-mode. > > How do you Qi4j guys handle model change over time for "already in > > production" applications ? > > Ok, we are not there yet. I'm not in a hurry :) > 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. Sounds nice, I'll keep reading this list and if something comes to my mind, I'll share with you. > This needs to be done either on per-object, or more preferably, > per-aggregate, level. Definitely makes sense to me. Best regards and thank you for such a piece of software. Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
