RE: Drop a user leaves permissions!
От | Matthew |
---|---|
Тема | RE: Drop a user leaves permissions! |
Дата | |
Msg-id | 183FA749499ED311B6550000F87E206C1FCFE4@srv.ctlno.com обсуждение исходный текст |
Ответ на | Drop a user leaves permissions! ("Trewern, Ben" <Ben.Trewern@mowlem.com>) |
Список | pgsql-general |
I have seen this before myself, and I agree it is less then optimal. I would think that it's a place where referential integrity should be used. Either don't allow you to drop the user until all permissions are removed, or automatically remove all permissions, cascade delete type of thing. > -----Original Message----- > From: Trewern, Ben [SMTP:Ben.Trewern@mowlem.com] > Sent: Tuesday, February 13, 2001 11:10 AM > To: 'pgsql-general@postgresql.org' > Subject: [GENERAL] Drop a user leaves permissions! > > I'm using PostgreSQL and I've been working with permissions. > I've tried the following: > > CREATE USER ben; > GRANT ALL ON table1 TO ben; > DROP USER ben; > > The permissions get left to the table as in : > > Relation | Access permissions > ------------------------------------------------------ > table1 | {"=","51=arwR"} > > I assume that 51 is the ID of the user who was dropped. > Is this a bug? How should I clean up the permissions? > > thanks > > Ben
В списке pgsql-general по дате отправления: