macOS Cocoa/Xcode Program - SQL Database Question

[Outie]

Hello again MacRumors,

Question:

1. If a database program is designed to run in OS X using Cocoa/Xcode does it matter what OS the database (PostgreSQL) is running on that the OS X program will access?

2. Is there a preference as far as speed and reliability is concerned?

3. I was thinking Ubuntu Server (or other distro), OS X Server, MS.

Thanks

 

[stomer]

2. Is there a preference as far as speed and reliability is concerned?

MySQL has been shown to be faster out of the box. PostgresQL has some features that are more mature, such as triggers and stored procedures. If you've ever used Oracle, then Postgres will seem more familiar than MySQL.

3. I was thinking Ubuntu Server (or other distro), OS X Server, MS.

I prefer Debian, which is what Ubuntu is based on. Very easy to install, by default it doesn't install an X server or a window manager. Also, FreeBSD would make a perfect server too. Although, FreeBSD setup is a little bit more involved than Debian's.

 

[Outie]

Stomer,

Thanks for the reply! I am still looking for an answer for question number one, one thing that comes to mind is if I am using an OS X server (managing users) and OS X clients and say the database is running PostgreSQL on a Debian Server, how is the permissions carried over to Debian?

Thanks

 

[stomer]

Stomer,
Thanks for the reply! I am still looking for an answer for question number one, one thing that comes to mind is if I am using an OS X server (managing users) and OS X clients and say the database is running PostgreSQL on a Debian Server, how is the permissions carried over to Debian?

I'm afraid I'm not sufficiently familiar with the workings of OS X server or Xcode in order to be able to answer your question probably.

As far as I'm aware, user management is managed using LDAP, and I'm not sure how a RDBMS fits into this.

When you mention permissions, which permissions? ACLs? Database permissions? If you mean database permissions, then you'd probably need to at least manually provide the program accessing the DB with a user/password and sufficient privileges. If the program is able to create its own users, then you'd need to make sure that the user(used by the program) has sufficient privileges.