How about the last_login and date_joined fields in the User model? They're both set to the current date/time when the user is created.
So, if the user's "first login" is when the account is created, you could check to see if they're less than a second apart. If the user is created automatically, then you can do the same check, and if they're still that close together then you know they've never logged in. I don't think there could really be any problem with race conditions, because both dates are initialized at the same time, when the user is created, so a delta of, say, two seconds should be more than enough. However, it does feel a little bit dirty to me. Not as dirty as having a boolean in a join table that has to be checked on every log in for the rest of the life of the application just for a single use, though. Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
