Slashdot Mirror
Names That Break Computers (bbc.com)
Reader Thelasko writes: The BBC has a story about people with names that break computer databases. "When Jennifer Null tries to buy a plane ticket, she gets an error message on most websites. The site will say she has left the surname field blank and ask her to try again."
Thelasko compares it to the XKCD comic about Bobby Tables, though it's a real problem that's also been experienced by a Hawaiian woman named Janice Keihanaikukauakahihulihe'ekahaunaele, whose last name exceeds the 36-character limit on state ID cards. And in 2010, programmer John Graham-Cumming complained about web sites (including Yahoo) which refused to accept hyphenated last names.
Programmer Patrick McKenzie pointed the BBC to a 2011 W3C post highlighting the key issues with names, along with his own list of common mistaken assumptions. "They don't necessarily test for the edge cases," McKenzie says, noting that even when filing his own income taxes in Japan, his last name exceeds the number of characters allowed.
Have you ever seen an application (web or otherwise) that tested an input field against the value "NULL" ? Yes: test if it is NULL (note the missing quote marks) or if it is the empty string, but not the string "NULL". I can, just about, accept that some programmer high on something illegal might have done so once, but the impression given by the article is that this happens a lot.
I find this hard to believe. If it were true then the applications involved would be open to worse exploits than simple SQL injection.
Data cannot break computers. Data whose contents differ from the possible preconception of application programmers can cause errors in poorly designed, written, or tested applications.
Most programmers can not even figure out how to validate a f--ing email address, let alone a persons name.
How about they fix the email problem first and stop rejecting my email address ^_^@mydomain
Yes, you can put that on my domain listed below and email me, and yes it is a valid email address as per the RFC.
Because the spec for email address is is ridiculously complex. The problem isn't that programmers can't validate email addresses, it's that they can't write good specs for email address in the first place.
Programmers who write database-aware programs that choke on the literal words, "null", "blank", or whose programs can't accept an apostrophe are simply incompetent or just plain stupid. There is absolutely no excuse for that kind of idiocy.
As long as your last name isn't a single letter. That catches my psuedonym fairly regularly.
Back when I worked in medical data, I encountered real people with single-character names. It happens for real names, too. For programmers, the rule is simple: Don't use names for anything except your application's convenience, and don't have any restrictions on them. Don't even require their existence.
You do not have a moral or legal right to do absolutely anything you want.