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: Daryl Stultz <kungfumachin...@gmail.com>
Date: Thu, 4 Mar 2010 13:27:16 -0800 (PST)
Local: Thurs, Mar 4 2010 4:27 pm
Subject: Re: Eager vs Lazy produces different results
On Mar 4, 3:37 pm, Rob Bygrave <robin.bygr...@gmail.com> wrote: > So, lets say each customer had tens of thousands of Orders Yes, I understand the challenge. As I said, when I first found that > you have some work to do to find > the list of unique customers first and then ... JPA did NOT filter the list I was surprised - you always get the whole list. Likewise, I was surprised that Ebean filtered the list. I definitely see it being useful to filter the list. My main point here is that I didn't *think* I was asking for a filtered list. Sometimes you want it one way, sometimes the other, and it needs to be clear what will happen. Perhaps the default should be to load it all to be consistent with JPA and JoinConfig should be used to specify that it should be filtered. Not sure that's the "Ebean way" to do it, but you see what I mean. > > JoinConfig().query() ... Yes, that's the second part of my complaint - eager does not produce > Hmmm, I'll have a look at that (I'd suggest that is a bug). the same as lazy. It seems like it would be easier to make eager return all than lazy return filtered, but that's your problem, right? :-) I'll try to put together a JPA example tonight. /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.
| |||||||||||||