I was looking at the 2 proposals for the future DB schema we are going to have and noticed that both these schema proposals use columns to represent user permissions.
…
With this kind of approach every time there is a new feature needed there will be a need to add another column and change the database schema.
So as a solution I suggest add another table which will hold each permission and its type.
TABLE UsersPermissions
In a similar approach shorten the UsersSuspensions Table
TABLE UserSuspensions
For reference:
I read through the feedback and updated the naming convention and the schema. Here is the new updated one.
Users
This table will hold the global user records for an Codidact Instance. A user should only have one email to login with, that would be stored here. I am leaving the password storage and hashing to the experts.
DisplayName (Text 100)
Bio (Text)
Personal Website (Text 255)
Github (Text 100)
Twitter (Text 100)
Email (Text 255) UNQIUE
GravatarHash (Text)
Location (Text 100)
IsF…
This is where I got to on the schema, please read my convention post first .
Users
This table will hold the global user records for an Codidact Instance. A user should only have one email to login with, that would be stored here. I am leaving the password storage and hashing to the experts.
Email (Text 255) UNIQUE
IsEmailVerified (Boolean default FALSE)
IsGlobalSuspended (Boolean default FALSE)
GlobalSuspensionEndDate (DATE)
Sites
Each of the individual sites inside of a Codidact instal…
3 Likes
I think that putting the specific privileges and suspensions into a separate table makes sense while IsSuspended can stay on the Users table.
Did you mean to say a reference table instead of an Enum?
1 Like
IsSuspended does make sense.
And yes reference table would be more correct
1 Like
I agree with this proposal - I was going to make the same suggestion.
It should also be explicitly defined that the lack of a permission indicates permission is denied for the action.