-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Improved permission system #208
Conversation
Feature: basic permissions system
Feature: control the system name
Fix: create table only if it doesn't exists.
Logout button
…ve the same JSON result used in other query runners
… when length of series stays the same.
…plicitly add filters here too.
Feature: filters for all visualizations and not only tables
it wouldn't draw the chart with stacking other than none.
Feature: import query from json file
Fix ECMDERR
Added support for running scripts as queries
Thanks, @christophervalles-hailo. I've had a few busy days, but hopefully will merge it tomorrow. |
migrator.add_column(models.User, models.User.groups, 'groups') | ||
|
||
models.User.update(groups=['admin', 'default']).where(models.User.is_admin == True).execute() | ||
models.User.update(groups=['default']).where(models.User.is_admin == False).execute() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using only the is_admin
flag is a problem, because since the introduction of the permission systems new users might have only the admin permission without this flag set. It's better to use either one of them and delete the permission column only after updating the group.
Hi guys,
This pull request is to improve the current role system. It adds the concept of groups, the permissions are per group instead of per user. A new feature has been added and it's the ability to filter what tables a group access, if you don't want to filter them you can just put an asterisk as wildcard.