Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Ebean ORM
Home
+ new post
About this group
Join this group
Message from discussion Eager vs Lazy produces different results
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Rob Bygrave  
View profile  
 More options Mar 7 2010, 3:00 am
From: Rob Bygrave <robin.bygr...@gmail.com>
Date: Sun, 7 Mar 2010 21:00:10 +1300
Local: Sun, Mar 7 2010 3:00 am
Subject: Re: [ebean] Re: Eager vs Lazy produces different results
Print | View thread | Show original | Report this message | Find messages by this author

>> The criteria on filterMany() affects the orders collection and not the

root.

Correct.

>> I could restrict the customers based on one property of orders
>> while filtering orders on a different property of orders.

Correct.

>> The behavior will be the same for default eager, join query, and lazy

loading.

Correct.

>> Multiple filterMany can be applied for different child collections

(though not fluid).

Yes - that is the plan... with a caveat that Ebean allows only 1 of them to
be a 'fetch join'
(so as to avoid SQL Cartesian products) so other joins would be 'query
joins' or 'lazy joins'.

>> I like it, I think "filterMany" is very clear.

Great. I think if we document it well with some good examples it should be
reasonably
clear.

Cheers, Rob.

On Sun, Mar 7, 2010 at 2:12 PM, Daryl Stultz <kungfumachin...@gmail.com>wrote:

> > I was thinking we could add something like:

> > Ebean.find(Customer.class)
> >   .where().startsWith("name","A")
> >   .*filterMany()*.eq("orders.status",
> > Order.Status.NEW).gt("orders.orderDate", lastWeek)

> Let me state the behavior as I understand it so we're all clear. The
> criteria on filterMany() affects the orders collection and not the
> root. I could restrict the customers based on one property of orders
> while filtering orders on a different property of orders. The behavior
> will be the same for default eager, join query, and lazy loading.
> Multiple filterMany can be applied for different child collections
> (though not fluid).

> I like it, I think "filterMany" is very clear.

> > Daryl, Mario ... are you happy to go with Option 2 ?

> Yes.

> /Daryl


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google