Andras/BoundlessFlowCampus2K

Fork 0

User database design #226

New issue

Closed

opened 2026-04-10 10:21:14 +00:00 by a24vinla · 10 comments

a24vinla commented

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

Collaborator

We need to design the database containing all user info. We also need to determine what should be stored. Should the layout config files also be stored in this DB?

Related Issues: #221 #148 #143

We need to design the database containing all user info. We also need to determine what should be stored. Should the layout config files also be stored in this DB? Related Issues: #221 #148 #143

a24vinla added the

backEnd

label

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

a24vinla self-assigned this

2026-04-10 10:42:37 +00:00

a22erigr was assigned by a24vinla

2026-04-10 10:43:31 +00:00

a24timsv was assigned by a24vinla

2026-04-10 10:43:32 +00:00

e24aleli was assigned by a24vinla

2026-04-10 10:43:32 +00:00

a24vinla referenced this issue

2026-04-10 11:23:08 +00:00

Create database for user settings and credentials #229

a22erigr commented

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

Collaborator

V1 ER diagram

# V1 ER diagram ![bild](/attachments/d02f050f-26e0-4be2-ae12-357b15ca4072)

bild.png

142 KiB

a22erigr added the

needs review

label

2026-04-10 12:01:33 +00:00

a22erigr commented

2026-04-10 17:31:10 +00:00

Collaborator

A list of possible things that the database should contain can be located at #221 (comment). Don't be afraid to add as you see fit.

A list of possible things that the database should contain can be located at https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/221#issuecomment-1858. Don't be afraid to add as you see fit.

a22erigr commented

2026-04-13 07:42:07 +00:00

Collaborator

V2 ER diagram

# V2 ER diagram ![bild](/attachments/cad5c7ca-f222-4e1f-8aba-30c6a10a2ec1)

bild.png

145 KiB

b24idalu was assigned by c24elipe

2026-04-13 07:43:57 +00:00

a22erigr commented

2026-04-13 08:00:11 +00:00

Collaborator

![bild](/attachments/56499446-7c82-4a68-95ee-ffe2dd8c6b3d)

bild.png

86 KiB

b24idalu commented

2026-04-13 08:16:43 +00:00

Collaborator

ER and UML diagrams look good, everything seems to be included from issue #221.
The "recent layout" in the table user seems to be missing from the UML, as well as grid settings in layout.

ER and UML diagrams look good, everything seems to be included from issue #221. The "recent layout" in the table user seems to be missing from the UML, as well as grid settings in layout.

b24krila was assigned by b24johka

2026-04-13 09:49:07 +00:00

b24idalu removed the

needs review

label

2026-04-13 10:12:37 +00:00

b24krila commented

2026-04-13 10:44:18 +00:00

Collaborator

The diagrams looks good, however I have some pointers,

In Usersettings, you are storing data that already is being stored in User, such as email and LName. These attributes don't really belong in a settings menu. I am not entirely sure but this might also break normalization rules, since you are basically duplicating the dependency UserID -> Email/LName across two tables which introduces redundancy and could create a transitive dependency which would break 3NF.

And something small would be even in a diagram try to stick to the conventions that have been made since whoever does make the database might follow the diagram quite closely which currently breaks the conventions stated here.

For example in the diagram we have FName which does not follow our naming conventions of using lowercase letters and underscores (e.g, first_name) We are also supposed to avoid abbreviations where its possible.

The diagrams looks good, however I have some pointers, In Usersettings, you are storing data that already is being stored in User, such as email and LName. These attributes don't really belong in a settings menu. I am not entirely sure but this might also break normalization rules, since you are basically duplicating the dependency UserID -> Email/LName across two tables which introduces redundancy and could create a transitive dependency which would break 3NF. And something small would be even in a diagram try to stick to the conventions that have been made since whoever does make the database might follow the diagram quite closely which currently breaks the conventions stated [here](https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/SQL-Standards). For example in the diagram we have FName which does not follow our naming conventions of using lowercase letters and underscores (e.g, first_name) We are also supposed to avoid abbreviations where its possible.

b24idalu commented

2026-04-13 10:53:16 +00:00

Collaborator

A question regarding mail/lname stored in usersettings, are they there to update mail/lname? Should these be functions instead?