Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQL #7

Open
NanoAi opened this issue Mar 5, 2018 · 0 comments
Open

SQL #7

NanoAi opened this issue Mar 5, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@NanoAi
Copy link
Owner

NanoAi commented Mar 5, 2018

Whenever user data is stored or edited it should be saved via SQL.
Things that should be handled in SQL are Warnings, Bans, Groups, Tags, and Access.

GroupsTags
User Group SubGroup
SteamID64 Admin Trial
User A B ...
SteamID64 Builder Coder ...
PermissionsTagPermissions
uid Group ParentID can_kick can_ban ...
1 Admin 0 true true ...
2 Trusted 1 true true ...
uid Tag tool_remover can_lua ...
1 Builder true false ...
2 Coder false true ...
  • Groups with a ParentID inherit all permissions from their parent.
  • Tags can be assigned and stacked onto any user.
  • Prefixes... can_ is for permissions, tool_ is for tools.

Logs should not be stored via SQL!

@NanoAi NanoAi added the enhancement New feature or request label Mar 5, 2018
@NanoAi NanoAi added this to the Base Admin Mod milestone Mar 5, 2018
@NanoAi NanoAi self-assigned this Mar 5, 2018
@NanoAi NanoAi mentioned this issue Mar 5, 2018
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant