cocoa touch - Is there a preferred method of database management/object persistence on the iPhone? -
I have seen many ways, and each has significant plusses and minuses. I am learning the development of iPhone, I am preparing a relatively simple app, which is at its core, in fact, 3 or 4 related organizations do not have more than CRUD operations.
The ActiveRecord type object is firmly implemented for the Cocoa Touch that I read about online which is usually sent to extremely slow.
The example I'm looking for is hardcoded in most of the online (especially the practical programmers screencast) SQL controller class, which does not 't ... seems to me right is very old school (But the old school may be the best in this case).
I know that we can not discuss SDK 3.0 here, but it is common knowledge that Coradata is coming to the iPhone, definitely << P> I did not try my Gauge Muller
Limit my audience (I'm not sure that I really care about it. It will be an app for sale, but I am not planning to replace my career )
So far FMDB, but I Rci things read.What are some of your experiences, what works, and what not. Where would you say that (still very newbie) iPhone programmers spend their time?
There is currently a lot of semi-raw SQL encoded because there is no built-in system for high level work is not. FMDB is a good way to do this, but it just keeps the SQLite call as something else objective. For some situations this is great but clearly not for everything.
If you are familiar with ActiveRecord, it may be useful for you, because its purpose is like ActiveRecord. I have not used it either, so I can not tell you how exactly it really is. If this does not seem right for some reason, then at the point to target 3.0 and using core data, it is probably best.
Comments
Post a Comment