Jump to content

Database Backend Suggestions


  • Please log in to reply
2 replies to this topic

#1
Table16

Table16

    InsanelyMac Protégé

  • Members
  • Pip
  • 23 posts
  • Gender:Male
  • Location:Dekalb, IL
I'm trying to develop a personal management application using Cocoa and I'm looking for a database backend solution. I read that there really isn't a clean way access MySQL (which I know and prefer, and if I'm wrong about this, please tell me). I want to do possibly a web interface to it down the line which is why I mentioned MySQL. This means a remote server that hosts the database and my osx application could manipulate data on that server. I also read that there is some sort of SQLite and PostgreSQL support. I'm not familiar with these technologies.

I'm just looking on suggestions on what the easiest route would be, or the most practical for what I'm wanting to do.

Thanks.

#2
bofors

bofors

    ConvertIt2Mac.com

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 3,462 posts

I'm trying to develop a personal management application using Cocoa and I'm looking for a database backend solution.


Umm... what about CoreData?

I read that there really isn't a clean way access MySQL (which I know and prefer, and if I'm wrong about this, please tell me).


I am not sure what you mean by "clean", but I would assume you could at least use NSTask to access MySQL. If performance is not critical that should be fine (that is, if for some reason you refuse to just use CoreData like you are supposed to).

I want to do possibly a web interface to it down the line which is why I mentioned MySQL. This means a remote server that hosts the database and my osx application could manipulate data on that server. I also read that there is some sort of SQLite and PostgreSQL support. I'm not familiar with these technologies.

I'm just looking on suggestions on what the easiest route would be, or the most practical for what I'm wanting to do.


As soon as you start talking about a web interface, I think you need to be considering Ruby on Rails instead of Cocoa (as I take "web interface" to mean browser interface, if you merely talking about a distributed application and having a Cocoa client access a Cocoa server then there is no need to consider Rails).

I think you need to decide whether this application is going to have a web interface or not before proceeding.

#3
TennisGeek

TennisGeek

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 127 posts
  • Gender:Male
  • Location:Boston 'burb, born in Japan
  • Interests:Tennis, Computer, Mac

I'm trying to develop a personal management application using Cocoa and I'm looking for a database backend solution. I read that there really isn't a clean way access MySQL (which I know and prefer, and if I'm wrong about this, please tell me). I want to do possibly a web interface to it down the line which is why I mentioned MySQL. This means a remote server that hosts the database and my osx application could manipulate data on that server. I also read that there is some sort of SQLite and PostgreSQL support. I'm not familiar with these technologies.

I'm just looking on suggestions on what the easiest route would be, or the most practical for what I'm wanting to do.

Thanks.


PostgreSQL or SQLite, because of the licenses, and the fact that both supports transaction.
MySQL may require a commercial license, and you'd have tough time with concurrency control.

-- TG





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   Web hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy