You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2018. It is now read-only.
First of all, thanks for really awesome framework, it looks much better than monstrous MagicalRecord.
I'm using ObjectiveRecord in one of my project, and it takes advantage of NSFetchedResultsController to display data in UITableView and UICollectionView. Now most ActiveRecord style methods allow to fetch data from CoreData, but we don't need that with NSFetchedResultsController.
I could, of course, define private category, and just use private method of ObjectiveRecord, but that's probably not good. It could be great, if ObjectiveRecord provided a way to get NSPredicates from fancy where: methods.
The text was updated successfully, but these errors were encountered:
@supermarin We could add - (NSPredicate *)wherePredicateFor:(id)condition, or something more suitably named. It doesn't seem as clean of an API, though, and it would likely be dropped for the next big release. Thoughts?
Oh crap, sorry i've totally misread this.
Not sure if we should expose predicates in the current api; I was thinking about a method that returns you a generated NSFetchedResultsController
First of all, thanks for really awesome framework, it looks much better than monstrous MagicalRecord.
I'm using ObjectiveRecord in one of my project, and it takes advantage of NSFetchedResultsController to display data in UITableView and UICollectionView. Now most ActiveRecord style methods allow to fetch data from CoreData, but we don't need that with NSFetchedResultsController.
I could, of course, define private category, and just use private method of ObjectiveRecord, but that's probably not good. It could be great, if ObjectiveRecord provided a way to get NSPredicates from fancy where: methods.
The text was updated successfully, but these errors were encountered: