On Mon, 17 Mar 2025 at 10:11, Aditya Toshniwal < aditya.toshni...@enterprisedb.com> wrote:
> > > On Mon, Mar 17, 2025 at 3:39 PM Dave Page <dp...@pgadmin.org> wrote: > >> Hi >> >> On Mon, 17 Mar 2025 at 09:39, Aditya Toshniwal < >> aditya.toshni...@enterprisedb.com> wrote: >> >>> Hi Dave, >>> >>> On Mon, Mar 17, 2025 at 3:00 PM Dave Page <dp...@pgadmin.org> wrote: >>> >>>> Hi >>>> >>>> On Mon, 17 Mar 2025 at 09:11, Aditya Toshniwal < >>>> aditya.toshni...@enterprisedb.com> wrote: >>>> >>>>> Hi Dave, >>>>> >>>>> Essentially, the permissions can be based on the menus: >>>>> >>>>> Object Explorer >>>>> >>>>> 1. Manage Server Create/Edit/Remove. >>>>> 2. Create database object (user could still be able to create >>>>> using query tool) >>>>> >>>>> Definitely not the second one. We shouldn't do anything that is >>>> enforced in the database server - it's unlikely the two permissions systems >>>> will remain in sync for more than a few minutes, and we shouldn't be >>>> duplicating server functionality anyway. >>>> >>> Yeah. So should I proceed with the implementation? >>> >> >> >> If that’s what Akshay wants you working on, then sure :-) >> > > I was waiting for confirmation if the pgAdmin team would accept it or not > :) > My concerns have been answered, so it's good with me. -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org pgEdge: https://www.pgedge.com
