Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SectionNameKeyPath cannot be transient? #123

Open
inPhilly opened this issue Jun 18, 2017 · 1 comment
Open

SectionNameKeyPath cannot be transient? #123

inPhilly opened this issue Jun 18, 2017 · 1 comment

Comments

@inPhilly
Copy link

I believe this is supposed to be a drop-in replacement for NSFetchedResultsController. NSFetchedResultsController allows a transient (non-persisted) property for sectionNameKeyPath. This is a very important aspect of NSFetchedResultsController. There are many times where sectionNameKeyPath is better not to be a persistedProperty. For example, we may sort the data by NSDate. Say there are 10 objects and each has a different date but is within the same month. SectionNameKeyPath would be a way that we could keep the sort order (date) yet not group the items by date, but by a broader grouping such as month or year. This is just one example; I have 10s of cases in my app where sectionNameKeyPath needs to be a transient (non-persisted) property. I simply cannot create an additional field each time I need a non-persisted sectionNameKeyPath. Since this is a drop-in for NSFetchedResultsController, which does offer that functionality, is this something that could possibly change for RBQFetchedResultsController? Is it on the roadmap at all, if this is still being updated?

@malhal
Copy link

malhal commented Jun 20, 2020

NSFetchedResultsController may work with a transient property as sectionNameKeyPath but you will soon discover why you shouldn’t. Every object in the fetch result gets faulted just to find out its section!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants