Comment 1 for bug 663024
Revision history for this message
| Paul Harrison (paul-francis-harrison) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I would recommend not worrying about performance unless it becomes an issue.
I like the idea of multiple attributes.
As I understand this, we are talking about two tables, people and names. Each name entry has a field, person_id, allowing a person to have multiple names. If each person entry had a primary_name_id field the primary name would be guaranteed unique, and the SQL would be fairly painless.
Not so keen on using this system for device, badge, blog, email, facebook. This is straying too far toward the Inner-Platform antipattern. For things that will not be displayed on the website, a freeform text field should suffice. Even for things that will be displayed on a the website, a freeform blurb is worth considering. Failing this, fields in the person table.