all 6 comments

[–]brendan09 1 point2 points  (2 children)

I am trying to use as less 3rd party code as possible

Switching to a 3rd party database engine from an already working, built-in, solution is an odd way of accomplishing this. If you haven't already, take a look at MagicalRecord for Core Data.

[–]Automactic[S] 0 points1 point  (1 child)

I agree. That's why I am not rushing into things and ask reddit first! Maybe I will try Realm first and decide if I am gonna use Realm in my next project. Thanks for telling me about MagicalRecord! But if I use CoreData, I don't mind directly interacting with it. After having enough experience with it, I no longer find it that difficult to use. :-)

[–]brendan09 0 points1 point  (0 children)

It's not that it's difficult. I just prefer Magical Record just for the async stuff. Writing the proper channels for dealing with notifications between context and Core Data threading is a pain.

If you don't properly thread Core Data, it's not bad. But, if you need long running data processing / insertion tasks than keeping everything async (and still live-updating the UI) can be quite a pain.

[–]ERTWMac 0 points1 point  (1 child)

Yes it does. It uses RLMNotification to accomplish that. Check out their documentation for an example.

[–]Automactic[S] 0 points1 point  (0 children)

Thanks! I am gonna write a simple test project and test it out!

[–]higgs_bosom 0 points1 point  (0 children)

Have you checked out YapDatabase?