I have a list of share prices with the properties dateTime
and value
.
Currently I am sorting the share prices when fetching them using a sort
I'm not sure how using an NSMutableOrderedSet would affect the underlying sqlite database. It is nice to think that it would store it in the order of the set, but the underlying implementation is a blackbox and I don't think there's any guarantee that it would work consistently, if it worked at all.
If it's a performance gain you are looking for, I would think adding an index to that attribute would be the best approach.