On 6/21/13, Apache Bloodhound <[email protected]> wrote: > #554: "Last Login" does not update > -----------------------+---------------------------- > Reporter: rjollos | Owner: rjollos > Type: defect | Status: accepted > Priority: critical | Milestone: Release 6 > Component: plugins | Version: 0.5.3 > Resolution: | Keywords: AccountManager > -----------------------+---------------------------- > > Comment (by astaric): > > I can confirm, that last_visit does not update after each login. > > However, both setups (bloodhound and trac) with the login options I tested > (!AccountManager, --auth, --basic-auth) behave in the same way, > "last_visit" time is only updated when > - session is created for the first time (first login) > - when session data is modified and sufficient amount of time has passed. > Only the first loggin satisfies this requirements and (in every setup I > have tried) creates a session record with last_visit filled in. The > following logins do not automatically modify the last_visit field. >
It should ... [...] > > We could touch the session data after each successful login, which would > keep this field (more) up to date, but the real solution would probably be > to store logins in a separate table. If we consider this an important > issue, we could propose a patch to !AccountManager or hack around to > manually update the last_visit time. > My suggestion is to keep it the way it is . More sophisticated behaviors should be implemented by plugins . -- Regards, Olemis.
