Easily find issues by searching: #<Issue ID>
Example: #1832
After executing the USE ROLE command, the dropdown does not get updated with the Role selected. See attached screenshot.
If you have a long script, it’s critical to know the current role any time before you execute the statement.
| Field | Old Value | New Value |
|---|---|---|
| Version | 21.0 | Future |
We typically populate the role drop down based on the roles assigned to the user that is logged in. We use SHOW GRANTS TO USER "ADSPARTNER1" to get this information. This is what the Snowflake database provides. Since there can be sub-roles assigned to the user indirectly, it is not possible to also populate the drop down with these sub-roles. Perhaps we can use a combination of these two queries to populate the drop down depending on the current users access:
| Field | Old Value | New Value |
|---|---|---|
| Summary | Snowflake improvement: Display Current Role after the USE ROLE command | Case# 01008206 - Snowflake improvement: Display Current Role after the USE ROLE command |
Hi Lisa and Tom,
I was reviewing old Deferred Development cases that were assigned to me, and I wanted to let you know that I have tested this on Aqua Data Studio 24.1.0-rc-1 and I was unable to reproduce this issue. Please find the SQL logs and screenshots attached from my test.
Was this issue already fixed on newer versions of ADS? Please advice if this request can be closed.
Thanks,
Diego
Hi Lisa and Tom,
I was reviewing old Deferred Development cases that were assigned to me, and I wanted to let you know that I have tested this on Aqua Data Studio 24.1.0-rc-1 and I was unable to reproduce this issue. Please find the SQL logs and screenshots attached from my test.
Was this issue already fixed on newer versions of ADS? Please advice if this request can be closed.
Thanks,
Diego
It might have indirectly been fixed. It is real old. Since Diego tested it and no error was found, I would close it as fixed.
It might have indirectly been fixed. It is real old. Since Diego tested it and no error was found, I would close it as fixed.
| Field | Old Value | New Value |
|---|---|---|
| Resolution | Fixed | |
| Resolved Date | Mar 26, 2025 6:10 PM | |
| Status | New | Closed |
Issue #15836 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
We typically populate the role drop down based on the roles assigned to the user that is logged in. We use SHOW GRANTS TO USER "ADSPARTNER1" to get this information. This is what the Snowflake database provides. Since there can be sub-roles assigned to the user indirectly, it is not possible to also populate the drop down with these sub-roles. Perhaps we can use a combination of these two queries to populate the drop down depending on the current users access: