Tickets :: Comment on [#855] default first listing in the Browse

* Your Email Address
* Spam protection	Enter the letters below: .__.. .. ..__. __. \| \|\|\/\|\| \|[__](__ \|__\\| \|\|/\\|\| \|.__)
Comment	>> What was the reason for the (composite) name field initially? > > > > I don't really remember, but my opinion now is that while seperating > the name field makes some things easier, it also implies that the > application knows what a name looks like in a way that's not always > going to be right - makes putting in an entry for a company more > awkward, for instance. > > > > Of course, if the program isn't going to make assumptions, then we > really shouldn't have the "sort by last name" feature either. > > > > If it's doable and not too confusing, I'd like to see us go to a > model where you can only sort by last name if last name is a seperate > field. That way it can be fast for everyone and there's the option to > have the composite name field for those who want it, without the > baggage of trying to treat it as anything other than a string.
Attachment
Watch this ticket