On 2009-12-08 14.14, philippe van dyck wrote:
Looks like all of this could be related to the infamous 'migration'
mechanism.
Yeah, it could be related to that, for sure. Basically, during migration
we could do automatic upgrade checking on value types. Or do nothing, if
we do the type name trick, in which case the mapping happens at runtime
and no migration of state is needed.
Is there anything planned regarding migration ? (Sorry but qi4j's
JIRA and Git seems to be down)
There is already a Migration API in qi4j-extensions. It allows you to
specify Entity-evolution quite a bit, with both upgrade/downgrade rules,
as well as custom "do-whatever-you-want" options.
Well, we already have support for collections (e.g.
Property<List<String>> stringList()), so isn't that enough?
Should be, Property<Map<>> does not work... but I can live with that
Well, Map should be mapped to JSON-objects rather than JSON-arrays,
right? Should be possible to do as well.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
