From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Peter Eisentraut'" <peter_e(at)gmx(dot)net> |
Cc: | "'hackers(at)postgresql(dot)org'" <hackers(at)postgresql(dot)org> |
Subject: | AW: [HACKERS] Create Group |
Date: | 1999-12-14 11:16:24 |
Message-ID: | 219F68D65015D011A8E000006F8590C603FDC1BE@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > > CREATE GROUP name [ WITH [ SYSID id ] [ USER name1, name2, ... ] ]
> > > ALTER GROUP name WITH SYSID id /* changes sysid */
> > > ALTER GROUP name ADD USER name1, name2, ...
> > > ALTER GROUP name DROP USER name1, name2, ...
> > > DROP GROUP name
>
> > I think a group can be interpreted somehow like a priviledge.
> > As such the statement to add or remove a user from a group
> > would be a "grant" statement.
>
> Not really, at least not in our context. A group is a collection
> ("group") of users which can collectively be granted privileges. For
> example, you can do grant select on your_table to group staff
> (even right
> now).
At least Informix and Oracle see it that way (and call it role).
The functionality is the same.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 1999-12-14 14:21:35 | Re: [PATCHES] createdb/dropdb fixes |
Previous Message | Peter Eisentraut | 1999-12-14 11:12:33 | Re: [HACKERS] Create Group |