Some Object graphs can not be built efficiently with a single query. This feature allows the developer to define multiple queries to build an object graph.
For example, when you have an entity with 2 or more OneToMany relationships a single query results in a Cartesian product which is generally expensive.
This is really a +lazy join that will instead be executed immediately after it's parent query has run.
If no batch size has been specified then it will use a default of 100.
List<Order> list = Ebean.find(Order.class) .join("customer", new JoinConfig().query(3).lazy(10)) .findList();
Find Orders.. then immedidately Load the first 3 customers referenced by those orders.. after that lazy load customers 10 at a time as needed
Home