Christian Reis wrote:
> Landed; also took the liberty of updating the navigation links.
>
> Note, however, Stuart, that the users in the list have NULL displaynames; for instance:
>
> https://launchpad.net/people/benno
There are 140 people with the empty string as their displayname. I've reset
these displaynames, setting the field to the same as their name field. I
don't think it is possible to set names to the empty string any more via the
UI. I'm adding a constraint to Person.displayname ensuring that it can't be
the empty string or contain nothing but whitespace.
displayname is NOT NULL, and we need to ensure
> The page was changed to cope with it but the other Person pages may not cope so well; should we update displayname = name when displayname is NULL?
There isn't much we an do about the remaining pathalogical cases where you
can create an invisible displayname (or nearly so) - its just a side effect
of using Unicode.
Christian Reis wrote: /launchpad. net/people/ benno
> Landed; also took the liberty of updating the navigation links.
>
> Note, however, Stuart, that the users in the list have NULL displaynames; for instance:
>
> https:/
There are 140 people with the empty string as their displayname. I've reset
these displaynames, setting the field to the same as their name field. I
don't think it is possible to set names to the empty string any more via the
UI. I'm adding a constraint to Person.displayname ensuring that it can't be
the empty string or contain nothing but whitespace.
displayname is NOT NULL, and we need to ensure
> The page was changed to cope with it but the other Person pages may not cope so well; should we update displayname = name when displayname is NULL?
There isn't much we an do about the remaining pathalogical cases where you
can create an invisible displayname (or nearly so) - its just a side effect
of using Unicode.
-- www.canonical. com/ www.ubuntu. com/
Stuart Bishop <email address hidden> http://
Canonical Ltd. http://