gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Managing staff (user accounts)


From: Jim Busser
Subject: Re: [Gnumed-devel] Managing staff (user accounts)
Date: Tue, 24 May 2011 12:00:35 -0700

On 2011-05-24, at 2:08 AM, Karsten Hilbert wrote:

> You need to quote:
> 
>       ALTER USER "any-doc" WITH ENCRYPTED PASSWORD 'any-doc2';
> 
> or else PostgreSQL will try to subtract "doc" from "any"
> which won't work.

added to wiki


>> So is any-doc not an actual postgres database user, just a value in a table 
>> used by the GNUmed application?
> 
> No, it's the database user.

So a GNUmed level user account is, at the same time, also a Postgres level 
account, and the relevance of calling it (at the same time a GNUmed account) is 
because such accounts represent a subset *within* all of the various users who 
could exist across (potentially multiple) Postgres databases.

Given that, at the same time, a separate Postgres schema might get deployed on 
the same machine for something like LSMB (unless this is a bad idea)… would an 
LSMB schema need to live inside a separate cluster or could it live in the same 
(default) cluster as GNUmed?

Does Postgres "track / manage" user accounts across schemas such that if James 
T Kirk were granted a GNUmed account

        jaki

then and if Kirk insists that (and we accede to allow him) to also operate the 
accounting program LSMB, would we register into LSMB the same account user

        jaki

so that Postgres can manage this user across both schemas, or must he be 
assigned a different user account name in LSMB? IOW does Postgres not care, and 
would it separately manage

        jaki (in GNUmed)

and

        jaki (in LSMB)

who might even be different persons despite that to set it up that way would be 
inadvisable?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]