This might be slightly off topic, but why is the last_login set to the current date when a user is created?
Wouldn't it make more sense for that date to be null until the user actually logs in? On Apr 5, 4:25 pm, Wesley Childs <childs.wes...@gmail.com> wrote: > Thanks for the advice. > > I'm going for boolean as I like the idea of flipping back on in the future > for special events. > > Thanks > > Wes > > On 5 April 2010 21:06, Owen Nelson <onel...@gmail.com> wrote: > > > > it does feel a little bit dirty to me. > > Me too, that way leads to deciding something is a witch just because it > > floats. Can't argue with a Bool, and also, it might eventually be nice to > > be able to flip the bit on a whim (say a user wanted that "out of the box" > > experience all over again). > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
