| From: | De Clarke <de(at)ucolick(dot)org> |
|---|---|
| To: | slajeunesse(at)sympatico(dot)ca |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Re: PostgreSQL reference manual (groups) |
| Date: | 1998-03-26 01:47:41 |
| Message-ID: | de-980325174739.A408944@celeste.ucolick.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas is right.
Hooray for "roles" -- this is indeed the only way to preserve
the DBA's sanity across personnel turnover in key entry and
front desk, etc. definitely a core item.
A place where Sybase falls on its heinie (yes, I can admit
that their engine is less than perfect :-)) is that users
can only belong to *one* "group". This is frustrating,
and I'd love to see the ability to associate users with
multiple roles, rather than creating an elaborate system
of hierarchical role defs.
Gee, this PG discussion just gets more and more exciting as
it goes on.
de
.............................................................................
:De Clarke, Software Engineer UCO/Lick Observatory, UCSC:
:Mail: de(at)ucolick(dot)org | "There is no problem in computer science that cannot:
:Web: www.ucolick.org | be solved by another level of indirection" --J.O. :
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Ridderbusch | 1998-03-26 07:44:50 | [HACKERS] string.h and strings.h in ecpg |
| Previous Message | Stephane Lajeunesse | 1998-03-26 01:25:00 | Re: [HACKERS] Re: PostgreSQL reference manual (groups) |