Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE
От | Thomas Lockhart |
---|---|
Тема | Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE |
Дата | |
Msg-id | 38BBD583.642CB33B@alumni.caltech.edu обсуждение исходный текст |
Ответ на | Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE (Karel Zak - Zakkr <zakkr@zf.jcu.cz>) |
Ответы |
Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE
|
Список | pgsql-hackers |
> plan make changes to acl/account code it must be non-isolate change (it > must include user-profiles ..etc). (IMO of course :-) While I'm thinking about it... The current acl storage scheme flattens the acl info into a single string, with a special character ("=" as I recall) to delimit the user/group name from the permissions. But by quoting the user name, it is possible to create a user name which contains an equals sign, screwing up the acl handling. If you are redoing the acls, a good first step is to fix this, perhaps by recoding the acl field into a structure with at least two fields for username and permissions. - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California
В списке pgsql-hackers по дате отправления: