• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MySQL privileges.

C

Carlis

Senior member
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...?
 
For each customer who saves/generates data in the database, store their user ID with the records. When they return to the website, only query those records that have their user ID.

techfuzz
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top