On Tue, Sep 2, 2008 at 12:29 PM, Thejaswi Puthraya <[EMAIL PROTECTED]> wrote: > For any general web-application, every user is expected to enter his > details like first name and last name so it's not a usual case to have > both of them empty.
I have several projects written in Django up and running right now, none of them (even the half or so that uses django.contrib.auth) uses the first_name and last_name for anything. If I need to have more than a *username* I use a field display_name in the profile-model. This elegantly gets around internationalization-problems: the japanese and hungarians get to see their own names as they expect them to be seen (family name first), to the limits of UTF-8, and even people like Banksy or Madonna or Prince are allowed to use the service (not that any of them ever would, mind). Most web services/sites, social or not, ask far more than is necessary anyway, but then I am a recovering cypherpunk... If the info isn't there, it can't be leaked. For the record, I'm European, and there are European countries where you need a license from the state and a certificate from the police to be allowed to build a database of people, if the people in question give the information freely or not. Furthermore, you must have a system in place for the people in question to be allowed to correct and/or remove their own info. Not needed with just a username =) HM, in CYA-mode --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
