• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
EOQualifier proper fetch across to-many?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

EOQualifier proper fetch across to-many?


  • Subject: EOQualifier proper fetch across to-many?
  • From: Jesse Tayler <email@hidden>
  • Date: Mon, 05 Mar 2012 15:43:04 -0500

is there a proper way to fetch across a to-many and not overkill the database?

if I wanted to return a list of recently used venues that the user has associated with posts they have authored, I'd want a distinct return of venues, each having a post->author being the user, but this query like this would just churn on the database wouldn't it?

I didn't see a "distinct" wonder fetch property either, don't I have to use something to ensure the list is returned without duplicates?

		EOQualifier qual = Venue.POSTS.dot(Post.AUTHOR_KEY).eq(user());
		ERXRestFetchSpecification<Venue> fetchSpec = new ERXRestFetchSpecification<Venue>(Venue.ENTITY_NAME, qual, null, queryFilter(), Venue.CREATED.descs(), 25);

what's the best practice on that kind of fetch?



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: EOQualifier proper fetch across to-many?
      • From: Kieran Kelleher <email@hidden>
    • Re: EOQualifier proper fetch across to-many?
      • From: David Avendasora <email@hidden>
  • Prev by Date: Re: Opinions on OpenJDK
  • Next by Date: Re: Filtering a non-EO in a display group
  • Previous by thread: Re: Filtering a non-EO in a display group
  • Next by thread: Re: EOQualifier proper fetch across to-many?
  • Index(es):
    • Date
    • Thread