Postgres Pro
Downloads
Home   >   mailing lists

Re: [pgAdmin III] #88: Function's access control list ambiguity - Mailing list pgadmin-hackers

From pgAdmin Trac
Subject Re: [pgAdmin III] #88: Function's access control list ambiguity
Date
Msg-id 065.c57a699cb25f2ab3e28f757444f95d69@code.pgadmin.org
Whole thread Raw
In response to [pgAdmin III] #88: Function's access control list ambiguity  ("pgAdmin Trac" <trac@code.pgadmin.org>)
List pgadmin-hackers
Tree view 
#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.chawla@enterprisedb.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

pgadmin-hackers by date:

Previous
From: Dhiraj Chawla
Date:
Subject: Re: Re: Missing REVOKE in SQL for functions with SECURITY DEFINER (or any function, really)
Next
From: Erwin Brandstetter
Date:
Subject: Re: Re: Missing REVOKE in SQL for functions with SECURITY DEFINER (or any function, really)