Well, the short version is CoreData & SQLLite will not help you in any way with 
MySQL.  As to using another framework or rolling your own, that largely depends 
upon your needs.  Obviously the GPL is not an issue if you are going against 
MySQL anyways, so I would probably look hard at not reinventing the wheel and 
using a preexisting framework.

Andy 'Dru' Satori

On Apr 27, 2010, at 9:04 PM, Joshua Tidsbury <joshua.tidsb...@ctv.ca> wrote:

> Hello everyone,
> 
> I'm in the process of developing one of my first Cocoa applications, and I'm 
> looking for some advice to keep myself from wandering into the wrong 
> direction.
> 
> The application I am going to be writing ultimately needs to access MySQL as 
> a datastore. I'd love to go with Core Data and SQLite, but based on some 
> reading, SQLite wouldn't be ideal if multiple clients were to be accessing 
> the same datastore.
> 
> So, the question is this: Would I be advised to use the MySQL C API and write 
> my own wrappers or use the slightly more recent mysql-cocoa framework at 
> http://code.google.com/p/mysql-cocoa-framework/ ?  Or perhaps a third option 
> I am unaware of?
> 
> Many thanks,
> Josh
> 
> 
> Joshua Tidsbury | Systems Specialist, Creative Technology Systems
> t 416.384.7253 | m 416.433.3968 | joshua.tidsb...@ctv.ca
> 
> 
> _______________________________________________
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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/dru%40druware.com
> 
> This email sent to d...@druware.com
> 
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to