On Thu, Jan 21, 2021 at 3:13 PM Dave Page <dpage@pgadmin.org> wrote:
This seems like a very bad idea. What if the user that has left was the user that setup 50 connections used by everyone else?
Deleting those shared entries is (I would guess) most likely *not* what the majority of users would want, and the current behaviour is definitely safest.
In the current implementation when the admin user gets deleted all "Server groups" created by that user are getting deleted, so if that admin has created any Shared server other users are not able to access it as its server group is not present in the database.
That seems bad. I would suggest we only delete the group if there are no shared servers left in it that would become orphaned. Of course, in that case we'll also need to reassign ownership of the group.
We should make this optional; i.e. ask the use if they want shared servers created by the user to be deleted. If they say no, they should be reassigned to another user; either the admin that's deleting the user, or their choice of user (a little more complex of course, but more flexible).
In the shared server table, we are creating entries per user, for deletion of non-admin user we can delete the shared server tables entries as it will not affect any other users. (because only admin users can mark the server as shared.)
In case of admin user deletion, will add an extra check as suggested.
Sounds good - thanks!
Please revert this, until the deletion is made optional.