RE: [PEAR] liveuser status

> From: Jeroen Houben [mailto:jeroen@terena.nl] > Sent: Friday, September 19, 2003 3:34 PM > Lukas Smith wrote: > > >Well its moving rapidly towards stable. > >The API is already stable. The sql schema should be stable with the next > >release. > > > >In terms of code stability it is already quite stable yes. > >I will be heavily testing it in the next weeks. > > > > > > > Cool, looking forward to using it. I had a quick look at the ERD and the > SQL file (postgres). I was just wondering about a couple of things: > > Why did you chose to use groups and a seperate table for subgroups? > Isn't it easier to have one table for groups with group_id and parent_id? Because subgroups are optional. > About the foreign keys on the SQL file. I saw a lot of foreign keys, but > no ON DELETE or ON UPDATE actions. Is that because you think users > should decide for themselves what should happen in these cases? Stuff like that is database specific. Actually foreign keys only show up in the ERD and not in the sql files. If you use our admin interface you don't need to worry about things like that anyways. > Can you say anything about the speed? Sometimes, for instance for > displaying the menu, you need to check permissions on say 90 areas to > generate a menu (e.g. areas they're not allowed to see, shouldn't be in > the menu). Does it perform well with that given all the joins, using a > database abtraction layer and all? I don't see a reason why it should perform slowly. The only issue I see here is when using the complex container with a lot of groups and implicit rights. Right now the rights are cached per session, so the initial session loading might take a fair amount of time if your rights structure is very complex. However we plan to change that in the future. Not clear when though. Regards, Lukas