Why does the popup not show users(/roles/groups/whatever) in popup for $OBJECT(role)$ and show them for $OBJECT(login)$ (which actually seems to be a non-existent keyword in PostgreSQL)?

Sat May 27, 2017 1:25 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6608

My wild guess, that's because of SA cross-platform support and the need to bridge the "naming" differences between different db types. Roles in PG are like logins in other systems if they're not "group" type roles. There are no users and standalone user groups. Groups are roles too with group attribute.

Mon May 29, 2017 11:45 am

gemisigo

Joined: 11 Mar 2010Posts: 1438

Yes, that's reasonable as an explanation why it has roles in popup for $OBJECT(login)$, even if the term 'login' seems not to exist in PostgreSQL. What does not make sense, however, is why not show them for $OBJECT(role)$ as well, which is what they are actually called there. You're correct that roles in PG are like logins/users when used to login, but they also behave like roles in other systems when they lack the canlogin property and are used for permission management.

Not showing them for $OBJECT(role)$ is somewhat counter-intuitive, imho.

Mon May 29, 2017 2:28 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6608

Your point is very reasonable. I'm going to enter this a n enactment request. Thank you very much for your feedback.

Mon May 29, 2017 3:57 pm

gemisigo

Joined: 11 Mar 2010Posts: 1438

Thank you very much.

Mon May 29, 2017 4:42 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6608

Please update "Schemas (PostgreSQL)" query in the option to the following

Code:

SELECT
nspname, 'SC', oid
FROM
pg_catalog.pg_namespace
WHERE nspname NOT LIKE 'pg\_%'
OR nspname = 'pg_catalog'