Interesting. This is a situation I'd prefer never occur anyway. IMO,
ToManyList should work like a Set with a defined iteration order. This
wouldn't necessarily preclude duplicates because the uniqueness would be
based on the key.
The trade-off is the overhead of managing those semantics. Alth
Hello,
In my code example, there is actually a bug.
Indeed, if I do:
List roles = getObjectContext().performQuery(query);
ToManyList tml = new ToManyList(this,"roles");
tml.addAll(roles);
writePropertyDirectly("roles",tml);
I will end up with twice the number of roles... In
