Andras/BoundlessFlowCampus2K

Fork 0

User tables for future database #221

New issue

Closed

opened 2026-04-10 09:00:38 +00:00 by a24vinla · 6 comments

a24vinla commented

2026-04-10 09:00:38 +00:00

Collaborator

To be able to support users we need to store relevant data. We need to design these tables.

Parent Issue: #143

To be able to support users we need to store relevant data. We need to design these tables. Parent Issue: #143

a24vinla added the

backEnd

label

2026-04-10 09:00:38 +00:00

a22erigr was assigned by a24vinla

2026-04-10 09:00:38 +00:00

a22erigr commented

2026-04-10 09:17:44 +00:00

Collaborator

Does a list of information that should be saved for each user exist or should i create one?

a22erigr commented

2026-04-10 09:51:45 +00:00

Collaborator

list of possible information that should be stored

Possible tables

User
- Stores private info about the user
Role
- Sore role specific information
Settings
- Stores the saved user settings
Layout

user table

UserId
- For students
  - a22erigr
- For teachers
  - andras.marki
FName
- john
LName
- doe
Email
- Maybe only store his mail. Can be accomplished with regex
- Student
  - a22erigr@student.his.se
- Teacher
  - andras.marki@his.se
Role
- Student
- Teacher
- other
  - IT-support
  - Administration
Password
- The password should be hashed
- Restraints
  - Min length
  - Must contain special characters

# list of possible information that should be stored ## Possible tables + User + Stores private info about the user + Role + Sore role specific information + Settings + Stores the saved user settings + Layout ## user table + UserId + For students + a22erigr + For teachers + andras.marki + FName + john + LName + doe + Email + Maybe only store his mail. Can be accomplished with regex + Student + a22erigr@student.his.se + Teacher + andras.marki@his.se + Role + Student + Teacher + other + IT-support + Administration + Password + The password should be hashed + Restraints + Min length + Must contain special characters

b24krila commented

2026-04-10 09:53:55 +00:00

Collaborator

I believe it does not exist, if you look at issue:#148 i have used some "examples" on what could be stored such as emails, ID, password and how that should be stored.
#148 (comment)

I believe it does not exist, if you look at issue:#148 i have used some "examples" on what could be stored such as emails, ID, password and how that should be stored. https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/148#issuecomment-1799

a22erigr commented

2026-04-10 10:18:23 +00:00

Collaborator

Fast sketch of how the tables relates to each other.

Open to suggestions

Each user has one settings
- Setting needs a user to exist
Each user can have multiple roles
- Can be a student that works extra as IT-Support
- Roles can exist independent of User

# Fast sketch of how the tables relates to each other. Open to suggestions ![bild](/attachments/596bf04d-541c-4233-8f97-067a10f9967d) + Each **user** has one **settings** + Setting needs a user to exist + Each **user** can have multiple **roles** + Can be a student that works extra as IT-Support + **Roles** can exist independent of **User**

bild.png

83 KiB

a22erigr commented

2026-04-10 10:19:26 +00:00

Collaborator

@b24krila wrote in #221 (comment):

I believe it does not exist, if you look at issue:#148 i have used some "examples" on what could be stored such as emails, ID, password and how that should be stored. #148 (comment)

Looking in to it

@b24krila wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/221#issuecomment-1862: > I believe it does not exist, if you look at issue:#148 i have used some "examples" on what could be stored such as emails, ID, password and how that should be stored. #148 (comment) Looking in to it

a24vinla referenced this issue

2026-04-10 10:21:14 +00:00

User database design #226

b24krila commented

2026-04-10 10:59:57 +00:00

Collaborator

The sketch works as a prototype, it shows the relations well and paints a clear picture.

The parts that might need more discussion which you might realize from issue #148 is how do we store emails as it can be referred to as "sensitive" information my solution pointed out in issue #148 is to encrypt/hash the email and store the encrypted for fast look up.

The same for password were we instead store a hashed password + salt, Where each time you login we hash the password entered with the salt and see if the stored value matches what was entered.

Then logically we do not need to store FullName for we can get that information from first name and last name.

The sketch works as a prototype, it shows the relations well and paints a clear picture. The parts that might need more discussion which you might realize from issue #148 is how do we store emails as it can be referred to as "sensitive" information my solution pointed out in issue #148 is to encrypt/hash the email and store the encrypted for fast look up. The same for password were we instead store a hashed password + salt, Where each time you login we hash the password entered with the salt and see if the stored value matches what was entered. Then logically we do not need to store FullName for we can get that information from first name and last name.