I am building an applet to be run on a MySQL database. The applet can be used by anyone who chooses to register on the website. The user can use the applet to generate data that is stored in the database. Now, next time they come around the data should still be there, but other users should NOT be able to access their data.
Now, I see three ways of acquiring this:
1) Create LOTS of databases, one for each user. Seems like that would require a lot of power?
2) Set privileges for specifik tables. Is that even possible?
3) Program the applet so that it 'refuses' to read the tables that the user should not be allowed to view. Does this mean very poor security? I'm not starting a bank, but I don't want it to be very simple to work around...
Are there other alternatives that I haven't considered...?
Now, I see three ways of acquiring this:
1) Create LOTS of databases, one for each user. Seems like that would require a lot of power?
2) Set privileges for specifik tables. Is that even possible?
3) Program the applet so that it 'refuses' to read the tables that the user should not be allowed to view. Does this mean very poor security? I'm not starting a bank, but I don't want it to be very simple to work around...
Are there other alternatives that I haven't considered...?
Facebook
Twitter