You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: