Crimson Wings's Profile
Reputation: 13 Tradesman
- Active Posts:
- 215 (0.1 per day)
- 11-July 09
- Profile Views:
- Last Active:
- Aug 29 2014 01:31 PM
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Who Cares
- Dream Kudos:
Posts I've Made
Posted 19 Aug 2013Yeah the thing is I'm not really giving everyone permissions haha. Man maybe I need to find a way to express myself better. /> Just the MySQL user(s) that will do the queries in behalf of the employees. Think of a MySQL user that I will grant "ALL PERMISSIONS" versus three different MySQL users that will have "SELECT', "INSERT", and "UPDATE" permissions separately, like.
dbuser_readonly. SELECT permissions.
dbuser_update. UPDATE permissions only.
dbuser_insert. INSERT permissions only.
In that way my employees who only have read only permissions would make the system issue their queries via the dbuser_readonly MysQL user.
Still I think you're right though. I just never heard of a system that has multiple MySQL users to begin with.
Posted 19 Aug 2013You have exhausted my knowledge on this subject (and I'm a little confused) but:
QuoteI have figured out my permissions system, I just don't know if the managing MySQL users should be many or just one MySQL user with all permissions in the database.
you should limit the number of people who have all permissions /> so this, in my mind, necessitates creating at least 3-4 different roles. Good luck.
Yeah, that's what I'm thinking, which is why I should have MySQL users with different permissions rather than one "master" MySQL user. My Employees themselves won't really have much "power" at all, but the underlying MySQL users they all share is what is worrying me.
That being said, you answered my question haha. Thanks. Hopefully more people will have more imput on this.
Posted 19 Aug 2013I'm actually talking about the MySQL users in the back-end.
The first app I'm building is to keep track of what actions an employee does with an external app. The thing is not all employees have permissions to update the external up with new data. Some of them will have their "account" in our company but they can only view their own personal data - to manage these users I'd like to create a back-end MySQL user with read-only permissions. Then for users that update the external app I need to log their actions in a new table - for this I want to have a MySQL user that has insertion rights only. I'm mostly talking about the database design and it's users rather than its front-end
I have figured out my permissions system, I just don't know if the managing MySQL users should be many or just one MySQL user with all permissions in the database.
Gah, I don't know if I'm being clear haha, but think of actual users who have their accounts as "Employees" and the MySQL users as the actual users only MySQL sees in the server.
- Member Title:
- D.I.C Head
- 23 years old
- May 20, 1992
- La Paz, Bolivia.
- Programming, nature, music making, graphic design, metal music, music in general. CS.
- Full Name:
- Andy Ibanez
- Years Programming:
- Programming Languages:
- Objective-C, (X)HTML (in all its variations), CSS, PHP, C++, C#, Python.