Re: [pgAdmin III] #88: Function's access control list ambiguity

From: "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org>
To:
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [pgAdmin III] #88: Function's access control list ambiguity
Date: 2013-04-22 10:34:48
Message-ID: 065.c57a699cb25f2ab3e28f757444f95d69@code.pgadmin.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

#88: Function's access control list ambiguity
------------------------------+---------------------------------------------
Reporter: Dmitry Samokhin | Owner: dpage
Type: bug | Status: closed
Priority: major | Milestone:
Component: pgadmin | Version: 1.14
Resolution: fixed | Keywords: function
Platform: all |
------------------------------+---------------------------------------------
Changes (by dpage):

* status: reopened => closed
* resolution: => fixed

Comment:

commit abc44d28db6da2a335760cb5451fefc0dd035f5b
Author: Dhiraj Chawla <dhiraj(dot)chawla(at)enterprisedb(dot)com>
Date: Mon Apr 22 11:28:16 2013 +0100

Handle default privileges to PUBLIC correctly.

Teach pgObject::GetGrant() that databases, functions and languages
have implicit privileges granted to PUBLIC, and that REVOKE statements
may need to be generated for them.

Ensure that affected object properties dialogues display the default
privileges so the user can revoke them if desired.

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/88#comment:4>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Erwin Brandstetter 2013-04-23 14:06:15 Re: Re: Missing REVOKE in SQL for functions with SECURITY DEFINER (or any function, really)
Previous Message Dhiraj Chawla 2013-04-22 10:34:18 Re: Re: Missing REVOKE in SQL for functions with SECURITY DEFINER (or any function, really)