On Tue, May 22, 2012 at 5:42 AM, Tibor Mlynarik <[email protected]> wrote:
> Interesting work in area of fetch optimization is AutoFetch[1,2] and I > think idea can be applied also for remote "batch" operations > optimization. Are you aware that most Qi4j persistence access is query-free? No joins, no ORM impedance mismatch, none of those tricky many-to-many join tables, compounded indexes and dozens of other tricks to get all of that working at all.... And I have no intention of introducing this complexity for object traversal retrievals, and instead rely on the fact that a non-RDBMS database can be (and some are) magnitudes faster in Identity-lookup than an ORM solution. So, the few cases where you might need to batch process thousands of "records" in one go, and performance is important for it, Qi4j is not the right tool (probably not Hibernate either). The query case is different, and not something I have my head tuned into at the moment. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
