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

How to customize the List Query View and the Database Connection option to be only available to a specific user? #688

Open
markmeplease opened this issue Nov 1, 2024 · 0 comments

Comments

@markmeplease
Copy link

markmeplease commented Nov 1, 2024

I am also developing a low-profile and very simple SQL Query Executor similar to this app. But this Django package is a great tool, way more advance to what I am developing. If I may, I would like to ask how to customize this package with these functionalities.

  1. List Query and List Query Log and Favorites: Show only what belongs to the user
  2. Database Connection: Add groupings (many to many to the Group model) for the database connection, and only show the database connection to the user where the user belongs. In my case, user group has different user credentials with different level of database accessibility.
  3. Only the superuser can delete the logs
  4. If the user is_superuser, the user can view all the logs and the database connections including the delete function
  5. How to also set the default exporter to excel.
  6. Also, how to set the custom login view for the safe login and where it redirects after login
  • as of now, I set the template_name of the SafeLoginView to 'core/login.html' which is my login template and add this to my project's urls path('accounts/profile/', lambda request: redirect('/login', permanent=False)), to redirect the login to my index.

I guess, these functionalities will greatly improve the use case of this app.

Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant