From: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
---|---|
To: | Michael Rasmussen <michaelr(at)porch(dot)com> |
Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Roles UI Difficult with large numbers of records |
Date: | 2017-11-12 06:15:22 |
Message-ID: | CAKKotZS8y04r=+GAyT6ndX9cY9UbFDVyy5YXLW3ND18sEP7hDA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Please create a feature request here
<https://redmine.postgresql.org/projects/pgadmin4/issues/new>
On Fri, Nov 10, 2017 at 3:57 AM, Michael Rasmussen <michaelr(at)porch(dot)com>
wrote:
> 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.)
>
>
>
> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Murtuza Zabuawala | 2017-11-12 06:20:30 | Re: PGadmin4 |
Previous Message | Murtuza Zabuawala | 2017-11-12 06:12:59 | Re: Encoding error while trying to examine table |