Comments on: Do we really need separate fields for first and last names?

by: membogg

Mon, 09 Jun 2008 01:53:36 +0000

think feedjack deals with feed names the way exactly you said.
and maybe it has something to do with denormalization ?

by: digital

Sat, 28 Jul 2007 06:48:09 +0000

firstname = models.CharField(('first name'), maxlength=30, blank=True) lastname = models.CharField(('last name'), maxlength=30, blank=True) nickname = models.CharField(_('nick'), maxlength=30, blank=True)

def getfullname(self): "Returns the firstname plus the lastname, with a space in between." fullname = '%s %s' % (self.firstname, self.lastname) return fullname.strip()

just like the code from django.contrib.auth, haha

by: Bjørn

Sat, 21 Jul 2007 04:54:44 +0000

Yeah, sorting does require a consistent way of dealing with it. More and more, though, people are searching instead of browsing, but even then you’ll need a way to order the search results, I guess. I was very surprised to hear that in Iceland they order people by first name in their telephone directory.

by: Adam

Fri, 20 Jul 2007 02:55:37 +0000

Uh oh, it ate my underscores. Imagine that every time the italics go on or off there’s an underscore.

by: Adam

Fri, 20 Jul 2007 02:17:09 +0000

But then we will probably also need a sort name field, like Musicbrainz uses to convert "The Books" to "Books, The". So fullname, sortname, and display_name.

Or maybe just fullname with family name first and then displayname? Nah, the Americans won't like it.