• 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
Curious about $SUBST_VARS within a SUBQUERY of a fetch request template
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Curious about $SUBST_VARS within a SUBQUERY of a fetch request template


  • Subject: Curious about $SUBST_VARS within a SUBQUERY of a fetch request template
  • From: email@hidden
  • Date: Fri, 28 Aug 2009 01:46:47 -0700 (PDT)
  • Importance: Normal

I just created a fetch request template in my MOM that looked like:
SUBQUERY(platformInfos, $each, $each.platformName ==
$PLATFORM_NAME).@count == 0

I then looked up the template in the code and attempted to use it in the
usual manner with:
fetchRequestFromTemplateWithName:substitutionVariables:

Core Data complained that it could not resolve the SQL for
$each.platformName == $PLATFORM_NAME, "because of the RHS".

I would have thought that this variable would be replaced as normal, even
though it is inside a SUBQUERY.  Does anybody know if this is officially
disallowed, or a bug, or just developer-error somehow?

If I replace the substitution variable in the template with a literal
string, everything seems to work.

Cheers

-- Luke


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: Reasons why QL would fail to create thumbnail?
  • Next by Date: Re: Alert dialog in agent app?
  • Previous by thread: Re: core-data app design question
  • Next by thread: Get error message about registered observers when Object receives dealloc message
  • Index(es):
    • Date
    • Thread