Re: Solaris 10 (64Bit) - Different Behavior on Privileges and Default Privileges Tab Pages of Properties Screen of Database and Schema on pgAdmin III

On Mon, 2011-08-29 at 16:51 +0200, Guillaume Lelarge wrote:
> On Fri, 2011-08-26 at 16:53 +0500, Kashif Zeeshan wrote:
> > pgAdmin III (Version 1.12.3)
> > OS = Solaris 10 (64Bit)
> >
> > Following are the differences in the behavior on Privileges and
> > Default Privileges Tab Pages when adding Privileges on the Properties
> > Sheet of Database and Schema on pgAdmin III.
> >
> > First Issue
> > =============
> > On Privileges Tab Page when a role is added without Privileges (click
> > on Add/Change button without selecting any check box in Privileges
> > section) then one row is added with role name in the list and when the
> > same role is changed by adding the privileges in the Privileges
> > section then the same row is updated but incase of Default Privileges
> > Tab (Table, Sequence and Functions sub tabs) when the same above steps
> > are followed then two rows are added, one with role name and second
> > with role name and the assigned privileges. One Row must be added on
> > Default Privileges Tab same as on Privileges Tab.
> >
> > Second Issue
> > ==============
> > After performing the steps in First Issue when the row is selected and
> > remove button is pressed on Privileges Tab then the row is deleted
> > from the list and now if Add/Change button is clicked (without
> > selecting any check box in Privileges section) then another row is
> > added with selected role. But on Default Privileges Tab (Table,
> > Sequence and Functions sub tabs) afrer deleteing the added rows if
> > Add/Change button is pressed (without selecting any check box in
> > Privileges section) then no new row is added with selected role. The
> > row should be added with select role on Default Privileges Tab same as
> > on Privileges Tab.
> >
>
> They are both issues we should take care of. I created a ticket to work
> on this later.
>

First issue is fixed. The second one is not really a bug, so I guess
we'll work on it for 1.16.

--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com