Thanks. I still consider this a usability bug. Even in enterprise IT, it is not uncommon to apply users directly to certain databases if there is only one user account that will be used to access a database (besides admin users, who are all probably members of a superadmin role). Also, given how Postgres has collapsed users into roles, it makes even less sense.
The Grant Wizard's *Privileges* tab definitely has a bug. It wasn't showing roles under *Group Roles*. And the *Group Roles* or *Login Roles* sections ought to be renamed to conform to standard terms or explained better. Aren On Wed, Apr 13, 2011 at 11:59 PM, Ashesh Vashi < ashesh.va...@enterprisedb.com> wrote: > Open File->Options. > Go to Preferences tab and select "Show users for priviledges" and then Ok > button. > > -- > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB INDIA: Enterprise PostgreSQL Company<http://www.enterprisedb.com> > > > > *http://www.linkedin.com/in/asheshvashi*<http://www.linkedin.com/in/asheshvashi> > > > On Thu, Apr 14, 2011 at 8:23 AM, Aren Cambre <a...@arencambre.com> wrote: > >> The Grant Wizard's *Privileges* tab only shows *public* in the dropdown. >> That dropdown shows nothing in the *Group Roles* or *Login Roles* >> section. >> >> By the way, below I meant that the dropdown on the *Privileges* tab isn't >> showing the roles. >> >> Aren >> >> >> On Wed, Apr 13, 2011 at 9:44 PM, Aren Cambre <a...@arencambre.com> wrote: >> >>> If I have a login role defined, the *Privileges *tab of the database >>> properties dialog does not show that role. It only shows group roles. >>> >>> Also, searches on Google suggest that "login role" or "group role" are >>> nonstandard terms. >>> >>> Aren >>> >> >> > > > -- > > > -- > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB INDIA: Enterprise Postgres Company<http://www.enterprisedb.com> > > > > *http://www.linkedin.com/in/asheshvashi*<http://www.linkedin.com/in/asheshvashi> > >
