|
The rule is that you use nvarchar to store names in the database. You could also do away with names altogether and just assign everyone a GUID at birth. Problem solved.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
John Simmons / outlaw programmer wrote: You could also do away with names altogether and just assign everyone a GUID at birth. Problem solved.
|
|
|
|
|
Can I have a matching bar-code?
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
John Simmons / outlaw programmer wrote: just assign everyone a GUID
After logging in your site:
Hello, 7798eded-dfac-406c-a49b-b031a7d1afc5
This sounds so accomodating.
|
|
|
|
|
Humans' names are in no way unique nor immutable.
If your system imposes rules above and beyond those of the domain it is modelling then there will always be problems.
Better to allow fuzzy-logic searching (or use some other unique key if you are able so to do)
|
|
|
|
|
Which doesn't change original question.
But that said you want to make something deterministic which cannot be.
If the person that first entered the first name as "nine" it is unlikely to help the second person if the actually spelling of the last name is "9" or "mine" (they heard it wrong.)
The only real rules
- Name cannot start with nor end with spaces
- Name cannot consist of nothing but spaces, which is basically same as first rule.
- Name must exist.
After that work on something much more important like insuring that each person gets a bill every month and that they actually pay it.
|
|
|
|
|
So if you want to test the integrity of a system name your child "SET @Students = '<[db].><[schema].>Students TRUNCATE TABLE ' + OBJECT_NAME(@Students)
you can short by short hand call him student 
So if the school he goes to registers his name and loses all their data it will be a sign that that school is not for your child 
»»» <small>Loading Signature</small> «««
· · · <small>Please Wait</small> · · ·
![Badger | [badger,badger,badger,badger...]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/badger.gif)
|
|
|
|
|
jschell wrote: - Name must exist.
Why?
(see originally linked article.)
|
|
|
|
|
Mark Whybird wrote: Why?
I doubt that assertion.
If a company wants to deal with an individual as a legal entity, then that legal entity must provide their legal name. If a company wants to deal with a person as a non-legal entity then they must decide if they want to deal with the person or not. If they do then the person must have an identifier that people can deal with.
Of course in the context of the discussion one can state that if a person refuses to provide a name, regardless of whether one exists or not, and the company requires it then the company should just not do business with that person. That exceptional case would be so rare and so non-economically impactful the company should just take that option.
|
|
|
|
|
First try: Just replace any special character or space with the wildcard character, then use LIKE to compare.
Second try: Use SOUNDEX.
Third try: Write your own SOUNDEX-like function. I did this with PostgreSQL, when I realized that some foreign names did not compare well. Eventually, though, I got tired of maintaining it, and just used SOUNDEX.
|
|
|
|
|
Duncan Edwards Jones wrote: Why do you need any rules at all?
Agreed. It's one of those conclusions that seems to take devs a while to get to. Rules for names? I don't even implement rules for email addresses. If I need your email to be genuine I'll send you an activation link, otherwise I'll make it optional and couldn't care less what you put in it.
Of course I always use "int" to store phone numbers cos that's just common sense!
|
|
|
|
|
F-ES Sitecore wrote: Of course I always use "int" to store phone numbers
And ZIP codes! 
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: And ZIP codes!
Yeah ... never mind that such area codes in other countries tend to have all sorts of alpha numerics in them.
And then you get the odd guy wanting to input his phoneword instead of a number ... since that's how he remembers it.
|
|
|
|
|
The other "falsehoods" blogs are worth a read as well:
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Many of the time assumptions listed are stupid.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
There is no point in establishing rules for ASCII names - simply because most systems now use Unicode which allows Chinese, Persian, Hindi, Russian, Japanese, Korean, Thai, ... you get the idea.
OK - I agree that name lookup is a problem with non-European names (and even some European style ones) but establishing rules for something that has pretty much been superseded already seems liek a waste of time and effort!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
In a previous position I seemed to spend most of my time replacing characters that were 'reserved' in the system. It was an absolute nightmare and was the result of some clever so & so deciding to escape certain characters for some reason that was never fully explained.
Apostrophes, commas, ampersands, tildes, back slashes, forward slashes. I hate them all!
I may not last forever but the mess I leave behind certainly will.
|
|
|
|
|
Well, here's the framework:
- A person has zero or more names, each consisting of zero or more characters.
- Surnames are given last, except in cultures where they are given first.
In cultures that give you names like those given to horses by breeder, have fun. - Everything else must remain unspecified lest we run into "year 2000-ish" problems when something new comes along.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
What about "the artist previously known as Prince, now known as this rather odd looking squiggle"? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I don't go on social media. It makes you itch.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Except he changed back to "Prince" in 2000. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Only when he realised even he couldn't read his signature!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
And all because Warner Brothers took out a Trade Mark on his name.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
