Le 27 août 2009 à 11:37, Rickard Öberg a écrit :
philippe van dyck wrote:
I am in the process of converting as much as possible all my
entities to values (my model was composed of entities only).
One of them (the Contract value) has 8 mixins and a 'base' value,
so yes I do use VC subtypes (the reason for my hack-see previous
message).
BTW, I think this specific _type field could be used for migration
purpose later... (by imposing a new type or mapping between old-
>new types).
Could you please tell me when you plan to implement the _type field ?
Well, the question is how to do it. Should it be done as I said,
i.e. if the instance matches the expectation then don't include it,
otherwise do, OR should it always be in the stored data? Kind of
like always including the namespace declaration in XML I suppose.
What are peoples thoughts on this?
I don't like the idea of storing FQDN in the stored data either, so if
we could avoid it and default to an internal lookup, +1
As I wrote, we could also see that as a migration hook and impose a
new type during the internal lookup...
my 2 cents,
phil
Also, FYI, there is no checking about circular references in VC
(stack overflows) and I don't understand the semantics of
Property<Entity> (it is allowed).
True. Don't use circular references :-) As for references to
entities, yes they are allowed, but I'm also a bit unsure about the
semantics actualy. I personally use EntityReferences explicitly,
rather than Entity references in properties.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
