macOS Which DBMS in Obj-C?

Buschmaster said:

...
Perhaps there is a better DBMS to use with Obj-C? It's for a class so it has to be a database, not a file system.

Click to expand...

If it is for a class assignment why care if it is "universal". It's throw-away code. The best thing to do is to go with what you know.

If you want "universal" then write to an ODBC interface and then you can swap in or out any DBMS you like. ODBC does force you to write to the lowest common denominator SQL but for a class assignment "common SQL" is not bad.

We can argue over which is "best" but for a class project you will likely not have 100 million rows of data in your tables and with modern DBMS servers anything smaller than that caches in RAM and is always fast.

Here's a recent comparison of a couple of MySQL DBMSs for OS X

http://theappleblog.com/2009/02/27/mysql-showdown-querious-vs-sequel-pro/


Edit: oops, you want to code - Sequel Pro is open source, maybe you could use code from it.

I haven't used mysql much, but i would assume there is a C library for it... why not just use that? If you want, you can write a very small Objective-C class to wrap the C calls.

-Lee