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

Feature request: take PostgreSQL 'SET ROLE' into consideration #1292

Open
hahnn opened this issue Sep 29, 2021 · 0 comments
Open

Feature request: take PostgreSQL 'SET ROLE' into consideration #1292

hahnn opened this issue Sep 29, 2021 · 0 comments

Comments

@hahnn
Copy link

hahnn commented Sep 29, 2021

Hello,

When creating a PostgreSQL connection, we can set the username and associated password to use to connect to the DB.
That would be really nice to allow the specification of a role name (PostgreSQL 'SET ROLE' command) in addition.

This feature would allow the ones that manage PostgreSQL environments having users that cannot do anything in PostgreSQL by default, because it's mandatory to sort of 'escalate' privileges using SET ROLE <other_role_name>.

That would mean when using the omnidb command line to create a new database connection, add an option to specify the role to take. Also update a GUI to introduce this new SET ROLE field.

For now, what we do is to add the SET ROLE command in the SQL editor in front of any SQL code. It works but it's just a little bit annoying :-)

Thanks and best regards.

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