Cocoa mail archive
Re: Learning SQLite by watching Core Data?
FROM : Jens Alfke
DATE : Mon Jun 23 23:44:06 2008
On 23 Jun '08, at 2:35 PM, David Carlisle wrote:
> I am studying an application design by implementing it with Core
> Data, then studying how I would move it to a platform where only
> sqlite is available.
Whew. If you want to implement an app the same way on a no-CoreData
platform, you're talking about basically re-implementing CoreData.
That would be a terrifyingly large and difficult task. Keep in mind
that CoreData has been in development in one form or another for about
15 years (it does back to NeXT's Enterprise Object Framework.) A lot
of the magic inside NSManagedObject relies on very sophisticated
manipulation of the Objective-C runtime.
If you want to write an app that's portable between CoreData and non-
CoreData platforms, I would suggest using one of the existing wrappers
(QuickLite or FMDB) instead of CoreData. They're not as powerful, but
you'll be able to use them on both platforms without having to change
your code.
> I'm happy with my approach. I modified ISavant's suggested Unix
> statement, realizing I needed a .sqlite suffix after my document
> name to make it work, so that answered that question.
SQLite doesn't care what the filename extension is, so that couldn't
have been the issue.
> Ilan noted that Core Data does "undocumented voodoo" with sqlite,
> which is good to be aware of.
And that statement was immediately denied by a CoreData engineer. I
have never heard of CoreData using any undocumented sqlite features.
—Jens_______________________________________________
Cocoa-dev mailing list (<email_removed>)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
This email sent to <email_removed>
DATE : Mon Jun 23 23:44:06 2008
On 23 Jun '08, at 2:35 PM, David Carlisle wrote:
> I am studying an application design by implementing it with Core
> Data, then studying how I would move it to a platform where only
> sqlite is available.
Whew. If you want to implement an app the same way on a no-CoreData
platform, you're talking about basically re-implementing CoreData.
That would be a terrifyingly large and difficult task. Keep in mind
that CoreData has been in development in one form or another for about
15 years (it does back to NeXT's Enterprise Object Framework.) A lot
of the magic inside NSManagedObject relies on very sophisticated
manipulation of the Objective-C runtime.
If you want to write an app that's portable between CoreData and non-
CoreData platforms, I would suggest using one of the existing wrappers
(QuickLite or FMDB) instead of CoreData. They're not as powerful, but
you'll be able to use them on both platforms without having to change
your code.
> I'm happy with my approach. I modified ISavant's suggested Unix
> statement, realizing I needed a .sqlite suffix after my document
> name to make it work, so that answered that question.
SQLite doesn't care what the filename extension is, so that couldn't
have been the issue.
> Ilan noted that Core Data does "undocumented voodoo" with sqlite,
> which is good to be aware of.
And that statement was immediately denied by a CoreData engineer. I
have never heard of CoreData using any undocumented sqlite features.
—Jens_______________________________________________
Cocoa-dev mailing list (<email_removed>)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
This email sent to <email_removed>
