We used last_login, but I recall that we had to explicitly update the field within our own login code for that to have relevant dates. We have a fairly long persistent session, so we ended up including some additional time stamps in our code (though another model) to keep track of the last time someone viewed an object, etc....
We never found that we had to resort to cookies, but that may just have been specific to our implementation. -joe On 1/6/07, Per <[EMAIL PROTECTED]> wrote:
James Bennett skrev: > On 1/6/07, Per <[EMAIL PROTECTED]> wrote: > > Fist i saved everything a user had seen and not seen in the database, > > but i think it will be slow when the site gets bigger, so i'm trying to > > find another way to do it. > > The built-in User model has a 'last_login' field which you might want > to use for this; just read that value whenever they come back to the > site, and use it to determine what new content to show them (and, of > course, remember to update it as needed). > I was thinking about using that, but i don't understand how it works, because sometimes it gets updated and sometimes not. I was maybe thinking about using a cookie, i don't know much about cookies, but do you think i could do this with cookies? >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
