Re: liveuser status

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? 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? 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? Thanks! Jeroen