{"id":440,"date":"2006-11-02T23:06:43","date_gmt":"2006-11-03T04:06:43","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/archives\/2006\/11\/02\/core-data-and-mysql-as-a-data-store"},"modified":"2006-11-03T23:58:03","modified_gmt":"2006-11-04T04:58:03","slug":"core-data-and-mysql-as-a-data-store","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2006\/11\/02\/core-data-and-mysql-as-a-data-store","title":{"rendered":"Core Data and MySQL as a data store?"},"content":{"rendered":"

I’ve been thinking a lot about Core Data<\/a> recently. It supports SQLite out of the box, and its rather scalable and fast. Main reason being sqlite3 is included on every desktop and server of OS X that has shipped since 10.4 (Tiger).<\/p>\n

It got me thinking about using MySQL as a data store. It will involve work, as Core Data itself is not extensible. And if written, will we have to embed MySQL into the application? What kind of problems will this pose? Licensing is the least of my worries, I’m thinking more from an application perspective.<\/p>\n

I haven’t played with the Enterprise Objects Framework (EOF) yet, but it allows custom SQL, and is available in WebObjects so its probably time to take a gander. Only real problem is its not in Core Data, thus not available in desktop applications. Then there’s AJRDatabase<\/a> which allows you to use EOF via Objective-C, which seems to be the missing link.<\/p>\n

And then, why MySQL? Because it might be cool to use FEDERATED tables? Especially if FEDERATED is extended to allow local modifications…<\/p>\n

Some useful resources: Core Data as a Cheap Database<\/a>, CoreDataWish<\/a>.
\n<\/p>\n

Technorati Tags: coredata<\/a>, macosx<\/a>, mysql<\/a><\/p>\n

<\/p>\n

Share this:<\/h3>