Re: permUser information
Lukas Smith <[email protected]>
| Newsgroups | gmane.comp.php.pear.liveuser |
|---|---|
| Organization | BackendMedia GbR |
| Message-ID | <[email protected]> |
Julien Hofstede wrote: > Why is the information like 'lastlogin', 'is_active' stored in > liveuser_users and not in liveuser_perm_users? I think it would be more > valuable to see when the last time was that perm user logged in regardless > what container was used rather than to know when each individual container > was used to login. And it would be more useful to disable a perm user and > disabling each container, rather than disable each individual container. It > would make more sense to me if you would have developed these functionality > for the perm_users first. there are historical reasons here. however you can get the behaviour you want with a custom observer. i dont see that either solution is better than the other, so i dont see that we should change this behaviour. > And in this point of view: would it be wise to add an table like > liveuser_user_info storing information like email, first name, last name, no, seems like a needless join, but once we move the admin auth container over to the sql generator you can do this. however this will mean that the client will no longer be able to fetch this information, since we dont dynamically generate joins inside the client. > function, department etc. If I would store this information in the > liveuser_users table and decide that I will no longer support the > DB-Container this information will not be available anymore. how so? what would you support instead? the xml container also supports custom fields. > Or: is the liveuser_users table designed to be both a user information table > AND an authentication table? yes, that is the idea. regards, Lukas Smith [email protected] _______________________________ BackendMedia www.backendmedia.com [email protected] Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07