All geek questions in one place

Master Data Compared to SQLitePersistentObjects

I am creating an application for the iPhone and I am trying to choose between two solutions for persistent storage.

Master data, or SQLitePersistentObjects . Basically, all my application needs is a way to store an array of model objects and then load them again for display in a UITableView. Its nothing complicated. Core Data seems to have a much higher learning curve than easy-to-use SQLitePersistentObjects. Are there any obvious advantages of using Core Data over SQLitePersistentObjects in my case?

+3
source share
5 answers

Take a look at this question. My answer to this question also applies to yours.

Core Data VS SQL Statement, which is gd for iphone development?

+1
source

As the author of SQLite Persistent Objects, I say: use Core Data.

I wrote SQLPO when Core Data does not exist on the phone. Although I am proud of what I did with SQLPO, and although I prefer some things about its approach more than Core Data (in particular, you do not need to maintain separate class files and a data model), the engine underlying Core Data is much more mature and has many more engineering hours invested in it. So I abandoned the development of SQLPO when Core Data came to the iPhone SDK.

, , , Core Data .

SQLPO , , , , , , Core Data.

+13

SQLitePersistentObjects.

, iOS 3.x, SQLPO . .. iOS 4, .

DB .

SQLPO , sqlite3_close, , .

, iOS4 didMovetoBackground. SQLPO.

+1

. . , Core Data . Core Data , ( ).

0

SQLitePersistentObjects aka SQLLite Persistent Objects is not the same as executing direct SQLite. This is ORM in its own right. I have not used it yet, but I wanted to correct the completely incorrect answer that the previous poster gave.

And I'm seriously considering using it because Core Data is a pain.

See: http://iphonedevelopment.blogspot.com/2008/08/sqlite-persistent-objects.html

0
source

Source: https://habr.com/ru/post/1733463/

More articles:


All Articles