I'm trying to wrap my head around dealing with people in a table that
have multiple names or akas.
I run an entertainment news site and have to deal with people like
Pamela Anderson (who was once Pamela Lee, Pamela Anderson Lee, Pamela
Denise Anderson), Eva Longoria (who's now Eva Longoria Parker) and
Courteney Cox, who's Courteney Cox Arquette.
I haven't really dealt with this yet, but I guess now I better handle it
before I get stung too badly.
Right now I have a people table that has:
PeopleID
First
Middle
Last
Display
URL
So as an example you'd have:
PeopleID: 1078
First: Eva
Middle:
Last: Longoria
Display: Eva Longoria
URL: evalongoria
It's worked well for me. I have a peopleinphotos table...add Eva to a
photo caption and it's just a matter of grabbing her id number (1078)
and putting it in the table with the photoid #.
She gets nominated, the input form looks up her id# and adds it to the
nomination table.
I've been lucky in that most entertainers keep their public and personal
names separate. But suddenly Eva wants her credits to read Eva Longoria
Parker. Sure I can add Parker to the Last field and remember to always
use Longoria Parker when I input new info, but what happens if she gets
divorced?
Just wondering how some of you have handled akas/aliases/divorces for
things like customer databases. How do you ensure that a name change
doesn't actually cause a brand new record for the person if the data
entry person uses the old name, etc.
Thanks for any advice.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
