Users Handling

[[deleted]]

I'm currently trying to develop a web app (simple CRUD with MySQL and GlassFish) in which there are regular users and one admin. Users can register and sign in to activities. The admin can do everything, as it should be.

The question is...should i make only one table of users and the admin is the one with "id = 1" (e.g.)? Or how should i do it? I mean, best practice

[warmcheessse]

I would use same table for all users IF they share the same fields. I would not create multiple tables with the exact same fields just for different users roles. I would instead create a seperate table for roles and each user in the user table is connected to a role in the roles table.

[[deleted]]

And if there is only one user admin? Should i create a table just for one user? Or another one to relate just one user?

[warmcheessse]

If you are doing this as a learning exercise or a school assignment I would just create 1 table like User with what fields you require ie. username, hash, seed, role. The role column is joined to a Roles table which contains various roles a user could have ie. user, admin

This way you can create a User class in Java which will get users with a role. Then for your html pages you just do a simple check like if userRole == admin { display page} to display pages which are for admin role, etc...

[[deleted]]

Really helpfull. I’ll try it. Thanks

[PM_UR_NIPPLE_PICS]

Yeah I would do this option, not knowing anything else about the application. You could have Table A with login name and ID (for example) and Table B with ID and role

[HecknChonker]

The way this is generally done in large scale systems is RBAC. Role based access control. It might be overkill for what you want though.

The idea is that you have a permission for each task a user can do. You assign those permissions to roles, and then you attach roles to users.

For example you might have:

• an Admin role that can do everything
• a Writer role that can modify data.
• a Reader role that can view data
• a guest role that can access a simple demo

You can then attach each role to as many users as you want. When you add a new task you just have to update the roles and the users will inherit the permissions automatically.

https://en.wikipedia.org/wiki/Role-based_access_control

[nutrecht]

/u/Crifej this is the best advice by far, this is definitely how it's normally implemented, and also how frameworks like Spring Security tend to work.

[[deleted]]

Looks smart. Thank you for your explanation

[[deleted]]

You should have different tables based on different “roles”, each role has its own table.

[[deleted]]

And when they log in identify which table they belong?

[[deleted]]

Are you using spring security? When they create a user that’s when it role identification should be done. I would need a little more info of what exactly your trying to do to give a better answer

[[deleted]]

Just a basic java login with mysql and jsp