In Xcode you can add \"Indexes\" for an entity in the data model inspector.
Optimizing Core Data searches and sorts
As the title says, indexing is to speed up searching and sorting your database. However it slows down saving changes to persistant store. It matters when you are using NSPredicate
and NSSortDescriptor
objects within your query.
Let's say you have two entities: PBOUser
and PBOLocation
(many to many). You can see its properties at the image below:
Suppose that in database there is 10,000 users, and 50,000 locations. Now we need to find every user with email starting on a
. If we provide such query without indexing, Core Data must check every record (basically 10,000).
But what if it is indexed (in other words sorted by email descending)? --> Then Core Data checks only those records started with a
. If Core Data reaches b
then it will stop searching because it is obvious that there are no more records whose email starts with a
since it is indexed.
How to enable indexing on a Core Data model from within Xcode:
or:
Hopefully they are equivalent:-)
But what if you wanted: Emails started with a
and name starts with b
You can do this checking INDEXED for name
property for PBOUser
entity, or:
This is how you can optimise your database:-)