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
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
 
Daryl Stultz  
View profile  
 More options Mar 5 2010, 11:51 am
From: Daryl Stultz <kungfumachin...@gmail.com>
Date: Fri, 5 Mar 2010 08:51:21 -0800 (PST)
Local: Fri, Mar 5 2010 11:51 am
Subject: Re: Eager vs Lazy produces different results

> We could for example do...
>Ebean.find(User.class)
>   .where().*subquery()*.in("validRoles.id",myRoles)
>   .findList();
>I'm not sure about "subquery()"

I can see something like subquery() being generally useful - not just
in the case of *toMany. As you've written subquery().in, something
like subquery().eq would be useful, too. Not sure how chaining should
work, if you want more than one criteria in the subquery. How would
things "switch back" to the root query (how would you add more
criteria, maybe even another subquery, on the root where).

/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.