I have recently been pondering names and the way we store them. Generally a person will have a First, Last and Middle name. If you want to be particularly complete you might add a suffix field, perhaps even a title field. So if someone wants to be "Dr. John Q. Public III", they can. But a person can have more than one honorific and more than one suffix. For that matter then could hve a hyphenate last name too. So what if you are "Dr. John Quintus Maximus Public-Doe III Ph.D. MD. RPh."? You could do:
Persons PersonID Prefix FirstName MiddleName LastName Suffix PersonHonorifics PHID PersonID Honorific PersonNames PANID PersonID NameOrderBut then it gets to be a bear to work with, and no one ends up using them anyway.
Is there a generally accepted "Standard Way" to store name data?
In databases, information is stored in tables, columns and rows for easy processing. That storage is managed by the DBMS – database management system. There are relational (SQL) and non-relational (NoSQL) databases. A relational database is generally said to be the most common kind.
Database storage structureAll the information in a database is organized and structured in database tables. These tables are stored on the hard disk of the database server. The database tables are usually divided into columns and rows, just like a regular graphic table.
Finally, you shouldn't store credit card information in your database unless you absolutely need to. This includes credit card owner names, numbers, CVV numbers, and expiration dates.
I prefer AD naming style
First Name givenName
Last Name sn
Initials initials
Display Name displayName
Description description
Office physicalDeliveryOfficeName
Telephone Number telephoneNumber
Telephone: Other otherTelephone
E-Mail mail
Web Page wWWHomePage
Web Page: Other url
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With