Roles UI Difficult with large numbers of records

From: Michael Rasmussen <michaelr(at)porch(dot)com>
To: "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>
Subject: Roles UI Difficult with large numbers of records
Date: 2017-11-09 22:27:39
Message-ID: AC1CACAA-B001-4427-BEEB-0F47F08490CC@porch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Could Groups and Logins be separated again?

I understand why it was thought it would simplify things if they were combined, but in an enterprise micro-services architecture there are a lot of records to scroll through. (Despite that being an even one thousand, I swear it isn’t a doctored screen grab.)

[cid:image001(dot)png(at)01D35966(dot)E56DC930]

If the desire is to make the top-level grouping of objects simple, I would advocate having a top-level group called Authentication and two sub-groups called Group Roles and Login Roles.

- Authentication

+ Group Roles

+ Login Roles

--

Michael Rasmussen

Sr. Data Engineer

Porch

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Murtuza Zabuawala 2017-11-12 06:09:08 Re: values not fitting in query result columns, and some ideas
Previous Message Scott Marlowe 2017-11-09 19:35:48 Encoding error while trying to examine table