Re: Open 7.3 items

On Wed, 14 Aug 2002, Lamar Owen wrote:

> On Wednesday 14 August 2002 03:29 pm, Vince Vielhaber wrote:
> > Hate to complicate things more, but back to a global username, say
> > you have user "lowen" that should have access to all databases. What
> > happens if there's already a lowen(at)somedb that's an unprivileged user.
> > Assuming lowen is a db superuser, what happens in somedb? If there's
> > a global user "lowen" and you try to create a lowen(at)somedb later, will
> > it be allowed?
>
> If the user 'lowen' is then expanded to 'lowen(at)template1' it would be stored
> that way -- and lowen(at)template1 is different from lowen(at)pari, for instance.
> The lowen(at)template1 user could be a superuser and lowen(at)pari might not -- but
> they become distinct users. Although I do understand the difficulty if the
> FQDU isn't stored in full in the appropriate places. So I guess the solution
> is that wherever a user name is to be stored, the fully qualified form must
> be used and checked against, with @template1 being a 'this user is
> everywhere' shorthand.
>
> But maybe I'm just misunderstanding the implementation.

I may be too, but what's wrong with just "lowen" being shorthand for
'this user is everywhere'? Does it also mean that we'd have a user
postgres(at)template1?

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev(at)michvhf(dot)com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
http://www.camping-usa.com http://www.cloudninegifts.com
http://www.meanstreamradio.com http://www.unknown-artists.com
==========================================================================