| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE |
| Date: | 2000-02-29 14:19:47 |
| Message-ID: | 38BBD583.642CB33B@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Baccus | 2000-02-29 14:30:59 | Re: [HACKERS] Re: NOT {NULL|DEFERRABLE} (was: bug in 7.0) |
| Previous Message | Zeugswetter Andreas SB | 2000-02-29 14:14:34 | Re: [HACKERS] Re: [SQL] prob with aggregate and group by - return s multiplesh |