On 2009-10-16 15.42, Mads Brøgger Enevoldsen wrote:
Isn't there also a problem with the many association? I mean wouldn't
you *have* to support some kind of pagination on that? Maybe that is a
modeling issue, but what if the domain suggest that you have a many
association containing 10000 or more entries. Then when reading the
entity, it will load all of the them in a list.
But pagination would pollute the api and will probably be tricky to
implement. Maybe it would be possible to do some automatic pagination
when persisting, i.e. storing 100 items and then pointing to the next
page. This does not solve the size issues, as you would get many more
entities in the data store then...
Yes, ManyAssociations as they are implemented in JDBM right now are
definitely not scalable. And this would be a general problem for
key-value stores as far as I can tell. Neo4j, of course, solves this in
a beautiful way. Neo4j, also, would solve these other problems as well,
since it deals with the two-level lookup as well.
For key-value stores I don't really know how to handle large
ManyAssociations. For small collections it seems ok to do it the way we
do it now, but for large ones they would definitely have to be paged, or
handled differently in some way. How, I don't know, and am very
interested in solutions (other than "use Neo4j").
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
