Skip site navigation (1) Skip section navigation (2)

Re: User mapping

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: User mapping
Date: 2011-03-24 19:49:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
Le 24/03/2011 11:21, Dave Page a écrit :
> On Wed, Mar 23, 2011 at 10:10 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
>> Hi,
>> I'm looking at adding user mapping support. My first idea was to add
>> them as children of foreign servers, but it doesn't seem this was a
>> really good idea. They have no OIDs, no owners, no comments... geez, no
>> nothing actually. They don't seem like objects, meaning they can't be in
>> their own node (with no OID, refresh wouldn't work for example).
> They do have OIDs - and even without, refresh can be made to work
> easily. We'd just need to refresh based on the unique key (umuser +
> umserver).

Don't remember what I did yesterday, but you're right. They have OIDs.
That's good news.

>> My second idea was to add a "User mapping" tab on the foreign server
>> dialog, so that we could directly add user mapping to servers. It still
>> seems a good idea to me.
> After thinking about it last night, I think the treeview is the
> correct method. Add a user mappings node under the server. You're
> correct in that is would be pretty simple, but that doesn't matter. I
> would expect to see two tabs on the properties dialogue, one with OID
> and username (and comment, if that is added in PG), and one with a
> listview of key/value pairs for the options, in a similar layout to
> the role/database variables tab.

Yeah, will do.


In response to

pgadmin-hackers by date

Next:From: Guillaume LelargeDate: 2011-03-24 20:14:32
Subject: pgAdmin III commit: Implements support for constraint trigger
Previous:From: Dave PageDate: 2011-03-24 18:43:40
Subject: Re: Debugger crashes when setting a value with quotes

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group