Re: EOSortOrdering and keypaths [SOLVED]
Re: EOSortOrdering and keypaths [SOLVED]
- Subject: Re: EOSortOrdering and keypaths [SOLVED]
- From: "Andrew R. Kinnie" <email@hidden>
- Date: Sun, 20 Jun 2010 12:47:07 -0400
| Wow, you guys didn't even give me time to heat up some nachos for lunch. I figured it was blindingly obvious, and I figured that would be the key path, my problem seems to have been that I was creating this in a static method on my Booking class for its default sort ordering . . . and I was confusing myself. So now I have Booking.PERFORMANCE_KEY + "." + Performance.PERFORMANCE_TYPE_KEY + "." + PerformanceType.NAME_KEY
Seems to work now now that I know that this was as easy as I thought it should be. Thanks for the help! On Jun 20, 2010, at 12:31 PM, Chuck Hill wrote: performance.performanceType.nameAny ideas would be appreciated. This seems like it should be obvious, but I'm drawing a blank.
Andrew
-- Chuck Hill Senior Consultant / VP Development
On Jun 20, 2010, at 12:38 PM, Luke Holton wrote: If you are performing the fetch on the Bookings entity, providing the EOSortOrdering with the keys path " performance.performanceType.name" should do the trick. Have you tried that? Regards, Luke Holton Tel: 602-279-4600 ext 622 Fax: 602-279-4768 Desert Sky Software: www.desertsky.comSpecializing in the design, development and hosting of database driven web applications.
|
_______________________________________________
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