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.

372 comments

  1. Our Cross to Bear by Anonymous Coward · · Score: 0

    Spare a thought for kids whose hippy parents thought "Anonymous McGuire" would be a good name to stick it to the man. Man.

    1. Re: Our Cross to Bear by Anonymous Coward · · Score: 1

      They get custom license plate of Lost Tag and are surprised by the result.

    2. Re:Our Cross to Bear by bondsbw · · Score: 2

      Says the person named "Anonymous Coward".

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    3. Re: Our Cross to Bear by KGIII · · Score: 1

      My retarded younger-self put my name on my license plate - while living in fairly rural environs. Yes, yes it was stupid and it meant that every time I did something stupid it would come to light quite quickly. I've not had a vanity plate since.

      It might be interesting to find out the internal codes used for license plate readers and then see if they're properly sanitizing their inputs. Does "stolen" flag anything? Does DBR-323 flag as wanted for questioning? Sure, many of us assume that they're properly dealing with inputs but I'm not willing to operate under any such assumptions. I've *seen* too many examples of bad code.

      --
      "So long and thanks for all the fish."
    4. Re:Our Cross to Bear by grcumb · · Score: 2

      Says the person named "Anonymous Coward".

      Noel's son, presumably. Posting incognito.

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    5. Re: Our Cross to Bear by Anonymous Coward · · Score: 0, Troll

      Your retarded present-self is no picnic either.

    6. Re:Our Cross to Bear by greenfruitsalad · · Score: 1

      germans and austrians are my main gripe. half of them put Dipl. Ing. into the 'first name' field. i get it, you're proud you finished school, but it is stil NOT your first name!

  2. L2Program, L2DB by carlhaagen · · Score: 0

    Really, this should not be a problem for anyone who gets paid for doing this kind of work.

    1. Re:L2Program, L2DB by Anonymous Coward · · Score: 0

      My (~800k) Slashdot nick was $RANDOMLUSER for years, then one day, an "update" to the Slachcode bork it for all time...

    2. Re:L2Program, L2DB by WarJolt · · Score: 1

      From my experience many companies do things on the cheap and then keep it around forever. Fortunately any robust ORM should make any name work with relatively little effort as long as the length is less than 255. Unfortunately many developers still write code like it's 1999.

    3. Re:L2Program, L2DB by infolation · · Score: 1

      And I thought the difficulties I encountered with my "REGISTER_GLOBALS" username would last for all time, but luckily that problem is now 'solved'.

    4. Re:L2Program, L2DB by Anonymous Coward · · Score: 0

      Your forgetting the skill level of the Indian kids who get paid to do this kind of work.

    5. Re:L2Program, L2DB by Anonymous Coward · · Score: 0

      Meh. I was like "it's written in PERL, what was I expecting?" Now I just tool around in my ~2M UID. Still irritating, nonetheless.

    6. Re:L2Program, L2DB by Caedite+Eos · · Score: 1

      Lost two low 4 digits accounts, because one had a "$" in it, and the other a "?".

      One was mine and one was "given" to me by a friend who walked away in disgust from all things IT.

    7. Re:L2Program, L2DB by MightyMartian · · Score: 1

      No fucking shit. I'm trying to imagine how a text field isn't either quoted or escaped, or better paramerized, but realizing that's what has happened here, I'm also wondering just how vulnerable these systems must be to injection attacks.

      First order of business, fire your developer with extreme prejudice.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    8. Re: L2Program, L2DB by Anonymous Coward · · Score: 0

      In a manner of speaking, it already is an injection attack.

    9. Re: L2Program, L2DB by UnifiedTechs · · Score: 1

      Or you could have just contacted /. And ask for a name change like I did when my "^" was no longer a valid character.

    10. Re: L2Program, L2DB by Anonymous Coward · · Score: 0

      We would like to forget their skill level. Shitty incomplete crap that we have to pay good devs to fix or rewrite because companies want to save a buck is definately something to forget.

    11. Re:L2Program, L2DB by david_thornley · · Score: 1

      Yeah. I get the same feeling from websites that will mail me my current password if I forget it.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  3. Updated Policy: by fuzzyfuzzyfungus · · Score: 3, Funny

    Users with unacceptably deviant names will be assigned GUIDs for standardized interaction with all systems. Thank you for your compliance with this exciting and mandatory efficiency initiative.

    1. Re:Updated Policy: by __aaclcg7560 · · Score: 1

      All users will be assigned Social Security Numbers for standardized interaction with all systems. Thank you for your compliance with this exciting and mandatory efficiency initiative.

      FTFY - That "problem" got fixed in 1987 when the IRS required Social Security Numbers to claim children dependents on tax returns. Your tax dollars at work.

      http://www.snopes.com/business/taxes/dependents.asp

    2. Re:Updated Policy: by angel'o'sphere · · Score: 1

      I'm pretty sure your system would reject my german social security number ... for no apparent reason.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    3. Re:Updated Policy: by rjune · · Score: 5, Informative

      After the IRS started requiring social security numbers to claim children dependents on tax returns, about 7 million of them vanished. In this case, it appears that the move was justified. http://www.snopes.com/business...

    4. Re:Updated Policy: by kesuki · · Score: 1

      Wrong, as with cod labeling all units will be assigned automatic, random, barcodes which are inked into their skin, resistance is futile death will be assigned to all non compliant software, including those with grandfathered unique names and social security numbers.

    5. Re:Updated Policy: by AmiMoJo · · Score: 1

      Seems like there should be libraries for handling names by now. Most popular languages have libraries for handling time, URLs, regexs, Unicode screw-ups, sanitizing input etc.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    6. Re:Updated Policy: by AmiMoJo · · Score: 1

      Actually, thinking about it this might be a problem that we can't solve today. For example, some people's names can't be written in Unicode, and even when Unicode does have the necessary characters there is no way to correctly render them for all Chinese, Japanese and Korean people. You have to pick one of the three renderings and Unicode gives you no hint which one.

      So the first step is to fix Unicode, which is kind of a massive undertaking.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    7. Re:Updated Policy: by Anonymous Coward · · Score: 5, Informative

      They do exist they are called string parsers.

      The real issue is that practically *any* integer could be a valid text character in any given input because of the number of codepages that exist. Then you have to take the trouble of identifying the specific codepage used by the input to know what can be safely excluded. Then you need to deal with non-printable control characters. Which amounts to reading bytecode from the input to make a decision on how to or what to interpret / print as a character. (Example UTF-8: First byte of any character is the number of bytes that compose that character (expressed in bits, and terminated by a zero bit.), unless it's one byte in which case the first bit is zero and the remaining 7 bits are the character data. Misinterpret a bit or get misaligned, and you start interpreting garbage.) Etc.

      Add all of this complexity to a short time span to develop libraries, (i.e. it needs to be done three days ago), and minimal budget, ("What do you mean we need to support diacritics? No we're not spending that money to add support for it. Ship the damn thing without it, if they want it they can pay for an upgrade.") and you can see why these problems exist. Mostly it's the idea that the support isn't needed for everyone so they can get away with not implementing it and blame any issues that crop up on the end user / some bug / a bad connection / etc.

      Sadly TFA is yet another call to attention for this issue, that ultimately will not be addressed unless it gets "fixed" by an unrelated upgrade / patch being rolled out that just so happens to fix these kind of issues, in addition to whatever the real purpose of the upgrade / patch was.

      PS: Read the summary, if "NULL" is considered a valid error result from a string parser, then that parser needs to be rewritten to support proper error codes. Practically anything could be valid input and returning the error status as part of the damn output string is ASKING for trouble. Why? Because then you need a parser to check the error status, so the original parser just made more work for the caller, and guess what? Something tells me the caller didn't check for the EXACT error string correctly, and thus interpreted "Null" as "NULL". Hence the error given to the user.

    8. Re:Updated Policy: by RabidReindeer · · Score: 1

      In related news, I once had a data download blow because someone was named Nuñez. The original mainframe system had fixed-length fields (as mainframe data often does). However, the original green-screen monitors had been replaced with Windows terminal emulators and someone had entered the actual n-tilde character that would have been impossible on the IBM 3270 US keyboard. So now we have a code that maps from ñ to n~ as it's converted from EBCDIC to ASCII, expanding the length of the field and thereby annoying the receiving software fatally. Had to add extra cleanup logic.

      Chtluhu alone knows what that customer's statements looked like. IBM mainframe printers weren't exactly stocked with extra characters either before laser printing took over.

    9. Re:Updated Policy: by Grishnakh · · Score: 1

      Why would it be a problem for Korean names? Korean has an alphabet with only 36 characters. It's not like Chinese.

    10. Re:Updated Policy: by HiThere · · Score: 1

      Is that really true for all representations of Unicode, or isn't it just true for the 16-bit version. I thought the full version of unicode only used 23-bit values because that's all there was any reason for. But I thought that utf-8 and utf-32 (ucc4?) were without the BLP problem.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    11. Re:Updated Policy: by KGIII · · Score: 1

      If true, the reason is readily apparent. ;-) Though the reason my vary, depending on the system in question.

      --
      "So long and thanks for all the fish."
    12. Re:Updated Policy: by KGIII · · Score: 1

      It seems like, other than the rendering properly issue, that might be easy enough to bang out a library for it. Are you sure such doesn't exist?

      I have no idea as I've never used it but I thought that's one of the things that libunistrings tried to deal with. I'm not sure how to approach those which will not render properly, regardless of the system in use. I suppose there's room to cram more characters into the spec?

      --
      "So long and thanks for all the fish."
    13. Re:Updated Policy: by KGIII · · Score: 1, Interesting

      > The original mainframe system had fixed-length fields (as mainframe data often does).

      Therein lies a part of why my username is what it is. I am not the exclusive user of it as a username but I'm probably the first. I've had it for a very long time. I've even been flattered by someone who was impersonating me at one point. The I looks a lot like a lowercase L in many fonts. KGlll is not that dissimilar to KGIII at first glance unless you're looking for it or a font guru.

      --
      "So long and thanks for all the fish."
    14. Re:Updated Policy: by Anonymous Coward · · Score: 2, Interesting

      Most Koreans have names comprising two to four Chinese characters which are then transliterated to Hangeul. (Source: I am one.) This Hangeul representation is then used in most cases in every day life, resorting to the Chinese in cases where homophonous names have to be distinguished, most commonly on government forms.

      However, nowadays more people are adopting "purely Korean" names, i.e. using Korean words with no Chinese representation.

    15. Re:Updated Policy: by doom · · Score: 1

      Are you sure that there are still names that can't be rendered in Unicode? My understanding was that they were continuing to assign codepoints in part to fix issues like that (there are still fun issues where some more primitive software have weak support for anything out of the Basic Multilingual Plane... good thing no one uses Javascript for anything much, eh? And the distinction between mysql's utf8 and utf8mb4 types can't possibly confuse anyone, could it?).

      You have a point about the difficulty of rendering CJK characters correctly: a hack built-in to the early 16bit version of unicode has han-derived characters sharing codepoints. There used to be a way to stick locale hints in, but that was deprecated with Unicode 5.0, damned if I know why.

    16. Re:Updated Policy: by Blaskowicz · · Score: 1

      Is it possible to know how many Chinese characters exist?, then work out those that are actually worth including.
      You could scrub thousands upon thousands of antique texts and include hundreds of new characters in the Unicode definitions, but most of them may be useless (e.g. truly unused in the last 500 years) or even errors.

      Are there characters used by maybe 50 people in rural China lurking somewhere? I suppose that instead of trying to solve this once and for all, we might only be able to discover those characters year after year and add them after the fact.

    17. Re:Updated Policy: by Blaskowicz · · Score: 1

      My first thought was that the language (be it Javascript or PHP) is too dynamic or weakly typed and converts a "NULL" string to a NULL type or value. But I tested for that : $a=("NULL" == NULL); and thanksfully that's false.
      Interestingly, in PHP the NULL is case insensitive! http://php.net/manual/en/langu...

      And guess what : in some countries it might be customary to enter the family name in all caps (in France on written forms at least).
      So, even if your parser or data entry doesn't uppercase the string it would be perfectly normal or even expected to have to deal with Jennifer NULL.

    18. Re:Updated Policy: by davester666 · · Score: 0

      The reason is because you are a Nazi.

      --
      Sleep your way to a whiter smile...date a dentist!
    19. Re:Updated Policy: by bytesex · · Score: 1

      To fix Unicode, you have to abolish it. And replace it with 16-bit characters. All schemes that try to do compression on numbers are bound to fail (I'm looking at you, BER). It's just too cumbersome.

      --
      Religion is what happens when nature strikes and groupthink goes wrong.
    20. Re:Updated Policy: by pjt33 · · Score: 2

      The characters which Unicode contains are independent of the encoding used to represent them. UTF-8 and UTF-16 can represent the whole (just over 20-bit) range of Unicode codepoints. The two problems described by GPP are unsupported characters and Han unification.

    21. Re:Updated Policy: by Ark42 · · Score: 1

      Quite frankly, Unicode works well right now, provided you use UTF-8 or UTF-32. UTF-16 and surrogate pairs is really quite an ugly hack, and 16-bits are obviously not enough when we need nearly 21 bits to encode all the existing characters already. UTF-8 is quite elegant (compatible with ASCII, but easily countable and self-synchronizing) and UTF-8 can easily be extended to 31 bits, should we need more codepoints in the future. UTF-16 can't be extended in any easy way and will just become a nightmare to support, should future versions of Unicode decide to start using codepoints above U+10FFFF

    22. Re:Updated Policy: by Ark42 · · Score: 2

      The issue isn't how many characters exist. There is room to add more characters to Unicode when missing ones are found. The big failure of Unicode is Han Unification, which is basically like saying "Well the character A in America has the same *meaning* as the character B in Canada, so let's only issue one codepoint for A/B" and now when you type an A on your American computer, all Canadian's see a B because their fonts render the exact same character differently. This happened with many common characters that have the same *meaning* in Chinese and Japanese, but are drawn completely differently. As an example, try to copy the Kanji at http://jisho.org/search/%E5%B0... into MS Word and compare the Meiryo font vs Microsoft YaHei font.

    23. Re:Updated Policy: by AmiMoJo · · Score: 1

      There are missing characters in CJK and Bengali at least, probably others. More than that though, to write a name properly you need to know which of the CJK renderings to use, and as you point out they removed all locale hints in Unicode 5.0. Even that was a horrible hack and made universal fonts impossible.

      That's why C/J/K airlines use older encodings like Shift-JIS. Passengers would be rather upset if their names didn't render correctly.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    24. Re:Updated Policy: by Rockoon · · Score: 2

      After the IRS started requiring social security numbers to claim children dependents on tax returns, about 7 million of them vanished.

      With justifications like this.... it is now far easier to consider things like drug testing welfare recipients.... require voters to have i.d's, and so on.

      --
      "His name was James Damore."
    25. Re:Updated Policy: by Rockoon · · Score: 1

      ..and this explains why there are so many oddball asian fonts on my clean win7 system. thanks!

      --
      "His name was James Damore."
    26. Re:Updated Policy: by Anonymous Coward · · Score: 0

      Why did you use an apostrophe to pluralize Canadian, but not on the dozen other plurals?

    27. Re:Updated Policy: by Anonymous Coward · · Score: 0

      Something tells me the caller didn't check for the EXACT error string correctly, and thus interpreted "Null" as "NULL". Hence the error given to the user.

      The problem is, fundamentally, the program equating the string "Null" to the value NULL. Capitalization is irrelevant, if the string has a value, then it should never be NULL in the first place.

    28. Re:Updated Policy: by doom · · Score: 1

      Yeah, like I was saying, that was a hack to try to squeeze all of the useful characters into the BMP, back when they were trying to limit the number of codepoints to 64k. Over 40% of the BMP is dedicated to Han-derived characters, there's no way 16bit unicode could've gotten close to working if they hadn't used this trick [1].

      So for CJK it's critically important to know the right font (or rather, to pick a font for the right culture), so for me the real question is why aren't there special characters built-into the spec that give you a hint about this? And there used to be a way to embed the locale, but now it's deprecated. WTF?

      [1] The OP here exaggerates how bad this problem is, I think: most differences between, say, Chinese and Japanese usage are more stylistic (to my uneducated eye, the Chinese fonts look like bold face, the Japanese a bit like italic). However, there are characters that have differences in strokes also, and we are talking about edge-cases here. It's pretty bad that hypothetically you could print someone's name in a way that doesn't just annoy them, but that they might not even recognize.

    29. Re:Updated Policy: by lsatenstein · · Score: 1

      Much less a problem in Quebec, Canada. Married name for spouse is surnameSpouse-SurnameHusband for most govt papers.

      --
      Leslie Satenstein Montreal Quebec Canada
    30. Re:Updated Policy: by lsatenstein · · Score: 1

      One should be hashing each alphanumeric input field on an input form in order to prevent hacker activities.

      --
      Leslie Satenstein Montreal Quebec Canada
    31. Re:Updated Policy: by kmoser · · Score: 1

      Names in cultures without written language will never be able to be rendered in Unicode unless you transliterate them.

    32. Re:Updated Policy: by Anonymous Coward · · Score: 0

      SSNs cannot start with 000, 999, or 666.

    33. Re:Updated Policy: by RockDoctor · · Score: 1

      All users will be assigned Social Security Numbers for standardized interaction with all systems.

      That would be [A-Z][A-Z] [1-9][1-9] [1-9][1-9] [1-9][1-9] [A-Z] then. Spaces may or may not be important.

      What? You assumed because I'm interacting with your government's systems, that your government has issued me with a SSN in your system, and that I'm aware of this assignment, and that I know what number has been assigned to me.

      "Assume". It's a big word for just 6 characters.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    34. Re:Updated Policy: by RockDoctor · · Score: 1

      Actually, thinking about it this might be a problem that we can't solve today. For example, some people's names can't be written in Unicode,

      One of the explicit entries on the "these assumptions are known to be wrong" list is "A person has a name".

      How exactly do you render "this person has not got a name" in UNICODE?

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    35. Re:Updated Policy: by Ark42 · · Score: 2

      95% of Han Unification doesn't seem like a problem to me. The slight stylistic differences between Chinese and Japanese where it's just a matter of "these tiny strokes point slightly left in Chinese and slightly right in Japanese" can still easily be understood no matter what font. Even slightly more stylistic differences don't actually cause any problems. For example, these two Kanji: http://jisho.org/search/%23kan... and other Kanji that have these shapes inside of them. The fonts tend to show the Chinese version: In the first, the top line is the same as the 3rd/4th, but Japanese usually write the top like a tiny dot almost, as seen in the stroke diagram graphic. In the second Kanji (scroll down), the last stroke is vertical in Chinese, but diagonal and connected differently in the Japanese version. Japanese people, in my experience, don't seem to have any problem with these kinds of differences.

      Other more major differences caused by Kanji simplification over the years has also resulted in two codepoints in Unicode, so the Chinese and Japanese characters that *historically* had the same drawing, are now actually usable in either language still. For example, https://translate.google.com/?... shows the Japanese and simplified Chinese "fish". Japanese still use 4 dots on the bottom, Chinese use a line. This was given two codepoints and doesn't seem to be a problem. Many other differences were given two codepoints and Chinese fonts typically don't include any definition for the Japanese version and vice-versa.

      The example I gave in my original post, about the Kanji meaning "leader" is one that really baffles me. Why was such a major difference in drawing merged into only one codepoint, and why was it never separated out into two codepoints in the next version of Unicode? There are other Kanji with major difference in appearance that share a single codepoint because of Han Unification, and these ones cause a lot of trouble. Japanese people typically don't recognize the Chinese version of "leader" as having any meaning at all. It's just scribbles to them, and when a webpage or document tries to display Japanese text but Windows or whatever decides to fall back to a Chinese font, the entire meaning is lost, because of Unicode.

    36. Re:Updated Policy: by Coren22 · · Score: 1

      Will it be on the forehead or the right hand?

      https://www.openbible.info/top...

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    37. Re:Updated Policy: by allo · · Score: 1

      [no name], but not in the name color, but in some gray.

    38. Re:Updated Policy: by allo · · Score: 1

      except for some people writing their own serialization.

    39. Re:Updated Policy: by Caesar+Tjalbo · · Score: 1

      I've installed a lot of Asian character sets and now see routinely weird characters pop up on websites. It seems that some arrows and other navigational character codes are also assigned to Vietnamese or Cambodian characters.

      --
      "I'm not much interested in interoperability. I want substitutability. I want to be able to throw your software out."
  4. Interesting read about names by angel'o'sphere · · Score: 3, Informative

    http://www.kalzumeus.com/2010/...

    Nothing to say, read it.

    There is similar stuff about Dates, Time, Time Zones etc. on the internet. I should make a collection of it.

    But I can't figure how to write into my /. journal nor how to use the old /. bookmark feature.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    1. Re:Interesting read about names by Athanasius · · Score: 3, Informative

      Someone already did: http://spaceninja.com/2015/12/...

    2. Re:Interesting read about names by Rockoon · · Score: 1

      I like how even the assumption that a person has a name is wrong.

      --
      "His name was James Damore."
    3. Re:Interesting read about names by Anonymous Coward · · Score: 0

      There probably needs to be one of those about money, too. (Though the "online shopping" one has a few points about money.)

      I remember back in the day I was working on a low-level driver to talk to a cash acceptor. The H1B conslutant working on the "authorizer" code (at a high level level it was being treated like a different kind of credit card payment) freaked out when I showed him a two-dollar bill. And yes, the hardware we were talking to recognized two-dollar bills.

  5. When it ends in PORN... by __aaclcg7560 · · Score: 1

    I was working the help desk at Intuit when a beautiful Indian woman employee required assistance with her laptop. Her last name was 26 characters long and ended with the word "porn". No one could pronounce her last name beyond the first few syllables. My coworkers and I referred to her as "Miss Porn" while repairing her laptop. Behind her back, of course.

    1. Re:When it ends in PORN... by Chewbacon · · Score: 1

      A user account feature of a company I worked for tried to censor names. Any name with any censored word buried in it got turned away. Mr. Brass and Mrs. Lassiter, we never got to serve them.

      --
      Chewbacon
      The Bible is like Wikipedia: written by a bunch of people and verifiable by questionable sources.
    2. Re:When it ends in PORN... by __aaclcg7560 · · Score: 2

      Mr. Brass and Mrs. Lassiter, we never got to serve them.

      I had a Chinese-American teacher called Mr. Fuch. The other teachers had a hard time trying not to mispronounce his last name. They all fucked it up.

    3. Re:When it ends in PORN... by samkass · · Score: 1

      I have this problem sometimes. My kids have my last name, Kass, and several of the new interactive things at Disney World a few years ago refused to accept their names, or later refused to accept my email address as a place to email their creations.

      --
      E pluribus unum
    4. Re:When it ends in PORN... by angel'o'sphere · · Score: 2

      Was more likely a Thai lady than an Indian.
      "Pon" or "Porn" is a common last syllable in Thai, for given names as well as family names.

      Perhaps she was Indian by birth but Thai by ancestry?

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    5. Re: When it ends in PORN... by skywire · · Score: 1

      That one took an extra-special exercise in stupidity to pull off.

      --
      Those who would give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety.
    6. Re:When it ends in PORN... by __aaclcg7560 · · Score: 1

      Perhaps she was Indian by birth but Thai by ancestry?

      Not sure how she came about the last name. Intuit had her stuffed into a small conference with 30 other Indians. They're all talking to each other while working on their laptops, which help desk couldn't fix because they were personal laptops. Their boss was a big guy in the center of the room who talked over them on a conference call. Weirdest scene I've ever seen in Corporate America. That was in 2004 or so.

    7. Re:When it ends in PORN... by Anonymous Coward · · Score: 0

      Their boss was a big guy in the center of the room who talked over them on a conference call.

      Well that definitely sounds like a fucking Indian.

    8. Re:When it ends in PORN... by Anonymous Coward · · Score: 0

      Just change your last name to Kbutt.

    9. Re:When it ends in PORN... by Anonymous Coward · · Score: 0

      I notice something similar when watching old TV westerns with the captioning on. Especially The Rifleman. Somewhere in the program chain there is a badword filter on the captioning. So every time Lucas (The Rifleman, himself) gets ready to fire his shotgun, the caption reads "-****S GUN-"

    10. Re:When it ends in PORN... by paiute · · Score: 2

      Lucas used a modified Winchester 44-40 1892 model rifle.

      --
      If Slashdot were chemistry it would look like this:Cadaverine
    11. Re:When it ends in PORN... by Anonymous Coward · · Score: 0

      Shut up. You're not funny.

    12. Re:When it ends in PORN... by __aaclcg7560 · · Score: 1

      Shut up. You're not funny.

      Is that you, Mr. Fuch?

    13. Re: When it ends in PORN... by Anonymous Coward · · Score: 0

      Shotgun? The word "rifle" in the title was a clue.

    14. Re: When it ends in PORN... by matt_hs · · Score: 1

      My principal's name in 7th and 8th grades was Mrs. Fuchs. St. Thomas More, Portland, Oregon. Try telling a bunch of middle-schoolers not to mispronounce that.

    15. Re: When it ends in PORN... by porges · · Score: 1

      You'd think the Disney people would be aware of people with names such as, just spitballing here, JOHN GODDAMM LASSETER. (Inspired by a reference two postings up, yes., Also -- with an E not an I? I never noticed that before.)

    16. Re:When it ends in PORN... by KozmoStevnNaut · · Score: 1

      It's a clbuttic mistake.

      --
      Eat the rich.
    17. Re: When it ends in PORN... by Anonymous Coward · · Score: 0

      My father worked with a woman named Fuxet. She insisted we pronounce it foo-SHAY. I always called her Ms. Fucks-It.

  6. Mysterious East by Anonymous Coward · · Score: 0

    It's amazing how many oriental names in Britain break UK databases! Especially if they're only two letters long.

    1. Re:Mysterious East by Hognoxious · · Score: 2

      Just move to Scunthorpe.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    2. Re: Mysterious East by BarbaraHudson · · Score: 1

      Try Dildo, NL. Or Swastika, ON.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    3. Re:Mysterious East by Teun · · Score: 1

      In the Dutch province of Friesland there's this town called Sexbierum.
      A few years ago these people regularly had trouble signing on to certain US based services.
      Quite surprising for a place where they shit in the restroom :)

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    4. Re: Mysterious East by armanox · · Score: 1

      No Intercourse, PA?

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    5. Re: Mysterious East by Anonymous Coward · · Score: 0

      woodcock ave

    6. Re: Mysterious East by Anonymous Coward · · Score: 0

      Climax, CO. Knob Lick, KY (lulz)

    7. Re: Mysterious East by Anonymous Coward · · Score: 0

      I wouldn't want to live in "Pernis" near Rotterdam.

    8. Re: Mysterious East by Anonymous Coward · · Score: 0

      Humpybong, Jimcumbilly, Mount Buggery, Smiggin Holes, Tom Ugly, Yorkeys Knob... Australia is unreal.

    9. Re:Mysterious East by KozmoStevnNaut · · Score: 1

      Or move to the Danish city of Middelfart.

      --
      Eat the rich.
    10. Re: Mysterious East by Teun · · Score: 1

      Neither do I, it's tiny and surrounded by the worlds largest refineries :)

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    11. Re: Mysterious East by Bahamut_Omega · · Score: 1

      Ragged Ass Road.

    12. Re: Mysterious East by Anonymous Coward · · Score: 0

      Knob Lick, KY, USA

    13. Re: Mysterious East by ncc74656 · · Score: 1

      ...or Fucking, Austria?

      --
      20 January 2017: the End of an Error.
  7. Hyphens in last names? by jader3rd · · Score: 4, Funny

    Just pick one already.

    1. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      How dare you imply that a strong womyn's name shouldn't be associated with her child for the rest of his life? You misogynist pig!

    2. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      Just pick one already.

      How would we know who the special little snowflakes are?

    3. Re:Hyphens in last names? by wisnoskij · · Score: 3, Informative

      More to the point, care about the future. Do you really want your children's children to be called Robert Smith-Schmidt-Maier-Kilgore? Not picking a single last name is just a huge FU to all future generations.

      --
      Troll is not a replacement for I disagree.
    4. Re:Hyphens in last names? by swb · · Score: 1

      Must have been what turned Leopold Ritter von Sacher-Masoch. He refused to accept having his name truncated and kept entering it despite the abuse he took.

    5. Re:Hyphens in last names? by JustOK · · Score: 3, Funny

      They dealt with that during the Name2K crisis

      --
      rewriting history since 2109
    6. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      " Do you really want your children's children to be called Robert Smith-Schmidt-Maier-Kilgore?"

      That's MY name you insensitive clod!

    7. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      More to the point, care about the future. Do you really want your children's children to be called Robert Smith-Schmidt-Maier-Kilgore? Not picking a single last name is just a huge FU to all future generations.

      Feminists don't think that far ahead. When all you care about is yourself, you don't need to.

    8. Re:Hyphens in last names? by PPH · · Score: 1

      I'm sure at one point this was discussed by Mr Cowboy and Ms Neal.

      --
      Have gnu, will travel.
    9. Re:Hyphens in last names? by Sigma+7 · · Score: 1

      Hyphenated names are a good way to merge families rather than demanding that the family lineage must go through the father and/or mother. If anything, it's progressive.

      For example, Mr. Johnson marries Miss Johnson, and decide to go for the classic hypenated name of Johnson-Johnson.

      Later, Mr. Johnson-Johnson meets Miss Johnson-Johnson, creating the new Johnson-Johnson-Johnson-Johnson family.

    10. Re:Hyphens in last names? by Anonymous Coward · · Score: 2, Informative

      wisnoskij,

      I trust you understand that hyphenated last names in English have a definite form.
      For example, Dr. Martin Lloyd-Jones used both his mother's and his father's last names in a hyphenated form.
      When children come about, one of the names, usually the mother's last name, is dropped.
      So Dr. Lloyd-Jones child would be come Robert Jones.
      Now Robert Jones may want his mother's name and become Robert Smythe-Jones.
      Only in America would the atrocity of a multiply hyphenated name stand a chance of occurring since Americans don't know customs or history.

    11. Re:Hyphens in last names? by Anonymous Coward · · Score: 1

      There is a very simple solution:

      In Spain and in most Spanish-speaking countries, the custom is for people to have two surnames. Usually the first surname comes from the father and the second from the mother, but it could be the other way round. A child's first surname will usually be their father's first surname, while the child's second surname will usually be the mother's first surname.

    12. Re: Hyphens in last names? by BarbaraHudson · · Score: 1

      Here the parents are allowed to give their kids hyphenated last names, but once they reach 18,they can use one or the other, or continue using both. The next generation, in the case where both parents have hyphenated names, can use either parents hyphenated name, but not both. They can also use one name for the kid, no hyphen. No way are we going to put up with that crazy crap of names growing crazily long like the Queen or other royalty. Sounds good much like a fancy show dog.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    13. Re: Hyphens in last names? by BarbaraHudson · · Score: 1

      And the blended family of Mr. Master and Mrs. Bates. Pity poor Johnny Master-Bates. Think of the children!

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    14. Re: Hyphens in last names? by Anonymous Coward · · Score: 0

      John-Jacob-Jingleheimer-Schmidt

    15. Re: Hyphens in last names? by fahrbot-bot · · Score: 1

      I like the system described in, if I remember correctly, the Arthur C. Clarke novel, The Songs of Distant Earth whereby a husband and wife kept their respective last names until their first child was born. If the child was a boy, they all took the husband's last name; if it was a girl, they all took the mother's last name.

      --
      It must have been something you assimilated. . . .
    16. Re: Hyphens in last names? by i.r.id10t · · Score: 1

      My daughter had some social issues with a class mate when she was in the 4th grade. We told her don't worry about it, in high school she'll get whats coming in the form of karma. The other girls name? Jenny Swallows.

      Here we are 6 years later, and yes, Jenny does have quite a lot to deal with at school....

      --
      Don't blame me, I voted for Kodos
    17. Re:Hyphens in last names? by AbRASiON · · Score: 1

      As someone who did account renames for a couple of years, I don't think this guy was joking.
      Hyphenated names are the worst, just comes off as some pretentious bullshit from someone who thinks they are hanging on to some heritage prestigious names. That shit is long gone, that era is gone, the people who had hyphenated names, 80 to 200 years ago? They probably came from a very wealthy family and were holding on to some kind of name that's been around for 1000 years, but nowadays? I can't help but feel it's some uppity girl who's still gonna be living in the suburbs driving an SUV to soccer practice in 10 years anyhow.

    18. Re: Hyphens in last names? by BarbaraHudson · · Score: 2

      Could create some problems if the first-born later gets a sex change :-)

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    19. Re: Hyphens in last names? by Anonymous Coward · · Score: 0

      Nah, do it like slavic cultures. Come up with a new name that blends both individual's name.

    20. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      If you think people in the future will be so helpless that they can't choose names that work for them without your present-day planning, you might be a narcissist.

    21. Re:Hyphens in last names? by sumdumass · · Score: 1

      Everyone i know of with hyphenated names ended up getting married after some professional career where the name had some value. One is a lawyer who had her own practice for 10 years before getting married. The other is a real estate agent who spent a ton marketing her name before getting married. The latter almost decided not to marry because of the issue.

    22. Re: Hyphens in last names? by Anonymous Coward · · Score: 2, Funny

      That's my name, too!

    23. Re:Hyphens in last names? by radarskiy · · Score: 1

      Why do you hate the Portuguese?

      https://en.wikipedia.org/wiki/...

      "It is not uncommon in Portugal that a married woman has two given names and six surnames, two from her mother's family, two from her father's family, and the last two coming from her husband. In addition, some of these names may be made of more than one word, so that a full feminine name can have more than 12 words."

    24. Re:Hyphens in last names? by jader3rd · · Score: 1

      The other is a real estate agent who spent a ton marketing her name before getting married. The latter almost decided not to marry because of the issue.

      She can always go by her maiden name professionally.

    25. Re:Hyphens in last names? by dbIII · · Score: 1

      The other option is to do what a lot of female doctors and scientists apparently do - just keep on using the same name professionally no matter what is happening with other social interactions.

    26. Re:Hyphens in last names? by Anonymous Coward · · Score: 3, Funny

      Y-TO-K STATUS REPORT

      Our staff has completed the 18 months of work on time and on budget. We have gone through every line of code in every program in every system. We have analyzed all databases, all data files, including backups and historic archives, and modified all data to reflect the change.

      We are proud to report that we have completed the "Y-to-K" date change mission, and have now implemented all changes to all programs and all data to reflect your new standards:

      Januark, Februark, March, April, Mak, June, Julk, August, September, October, November, December

      As well as: Sundak, Mondak, Tuesdak, Wednesdak, Thursdak, Fridak, Saturdak

      I trust that this is satisfactory, because to be honest, none of this 'Y to K' problem has made any sense to me. But I understand it is a global problem, and our team is glad to help in any way possible.

      And what does the year 2000 have to do with it? Speaking of which, what do you think we ought to do next year when the two digit year rolls over from 99 to 00?

      We'll await your direction.

    27. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      Once upon a time, authorities refused to acknowledge that a father even existed if a couple was unmarried. Simply put, the father's name was not recorded on the birth certificate (or on any other official record). In my case, I ended up with a double last name to avoid confusion if custody every became an issue.

      The funny thing is that double last names breaks people more than computers. People refuse to accept the existence of non-hyphenated, double last names. Modern software is okay with that. (Older software was fine with it too, though there were issues due to the length.)

    28. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      For the same reason I hate americans for sticking to shitty measuring units. And for the same reason I hate the french for the soixante-dix and quadre-vingt... soixante means sixty, and soixante-dix means sixty-ten or seventy. And vingt means twenty, and quadre-vingt means four times twenty, or eighty. Just a smidge of insanity, that chips off Your reasoning bit by bit.
      Drop the traditional cruft, for fucks sake. Make things simpler. Surely, such a system of names was required to be sure I wasn' t marrying my cousin, but now I dare say that we have family registers for this sort of thing. Even in Portugal.

    29. Re:Hyphens in last names? by Anonymous Coward · · Score: 0

      Major Major Major Major.

    30. Re: Hyphens in last names? by Anonymous Coward · · Score: 0

      Here's a solution that everyone can hate equally.
      Let's just dispence with names all together, and simply issue serial numbers to all newborns.
      It would prevent confusion for computers, simplify life for programmers, and finally it would reduce the number of mis-identifications to allmost null... errr nil.
      (Yes.. I did spend far too many years reading Mad Magazine.)

    31. Re:Hyphens in last names? by serviscope_minor · · Score: 2

      The other is a real estate agent who spent a ton marketing her name before getting married. The latter almost decided not to marry because of the issue.

      That's about the silliest thing I think I've ever heard. It's not like (a) you have to take a new name when you marry or (b) you can't take it but use your old name as a professional alias.

      --
      SJW n. One who posts facts.
    32. Re:Hyphens in last names? by Rockoon · · Score: 1

      Indeed. Your trade name does not need to match your actual name. Hollywood has known this forever.

      --
      "His name was James Damore."
    33. Re:Hyphens in last names? by ColdWetDog · · Score: 1

      For the same reason I hate americans for sticking to shitty measuring units. And for the same reason I hate the french for the soixante-dix and quadre-vingt... soixante means sixty, and soixante-dix means sixty-ten or seventy. And vingt means twenty, and quadre-vingt means four times twenty, or eighty. Just a smidge of insanity, that chips off Your reasoning bit by bit.
      Drop the traditional cruft, for fucks sake. Make things simpler. Surely, such a system of names was required to be sure I wasn' t marrying my cousin, but now I dare say that we have family registers for this sort of thing. Even in Portugal.

      Why hello 51787515-28387497! Haven't seen you in a while. How are the surrogates?

      --
      Faster! Faster! Faster would be better!
    34. Re:Hyphens in last names? by Megane · · Score: 2

      Not very well know fiction relating to this: The Man Whose Name Wouldn't Fit: Or, The Case of Cartwright-Chickering

      One-line synopsis: Arthur Duane Cartwright-Chickering, is fired from his job because the new computer that processes employee files cannot handle his long name.

      I have a copy of it somewhere, under stuff. I'd read it if I knew where it was right now.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    35. Re:Hyphens in last names? by tibit · · Score: 1

      WTF are you going on about? My maternal grandma, my mother, and my wife all have hyphenated names, and that has nothing to do with prestige, it's their personal choice. They could have had their names changed to anything they wanted - including Scunthorpe, for all I (and the law) cares. Why do you have such a problem with a fucking hyphen? The names that go on either side of it don't really matter. They are arbitrary strings, you idiot.

      --
      A successful API design takes a mixture of software design and pedagogy.
    36. Re:Hyphens in last names? by AbRASiON · · Score: 1

      I never claimed it was a rational dislike, but people with hyphenated names come across as complete twats. Sorry. I think you'll find it's not an uncommon opinion either.

      Can't help it! Not rational! Just they are awful, pretentious people, sorry.

    37. Re: Hyphens in last names? by Anonymous Coward · · Score: 0

      So what about twins: a boy and a girl? The first to come out wins? What about if a boy was set to come out first naturally, but something went wrong and the girl had to be cut out first?
      Always the edge cases...

    38. Re:Hyphens in last names? by tibit · · Score: 1

      OK, I've just learned that 1/7th of all married Polish women are, according to you, "complete twats", and that, somehow, that's not an uncommon opinion. Where the fuck do you live and what idiots think that way?! Never mind that in some countries, like Poland, having a hyphenated last name and being female leads to higher wages. So, following your inane worldview would leave a female at an economic disadvantage. Yeah, there are real studies about it.

      Basically, in some countries it's entirely normal for a female to change to a hyphenated name upon marriage, and some men do it too at that time.

      --
      A successful API design takes a mixture of software design and pedagogy.
  8. Aw, come on ... by Alain+Williams · · Score: 3, Informative

    Her name in a (web) form would be put into a database field as a string ... the word NULL is a keyword, not a string "NULL". I am not saying that this did not happen, I just find it hard to see how a string and a database keyword could possibly be confused ?

    It would be: INSERT INTO Customer (Surname) VALUES ("NULL")

    not:: INSERT INTO Customer (Surname) VALUES (NULL)

    1. Re:Aw, come on ... by Anonymous Coward · · Score: 1

      Obviously the problem is not with the database parsers, it's in the web application stacks that eventually compose the SQL query.

    2. Re:Aw, come on ... by Alain+Williams · · Score: 4, Insightful

      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.

    3. Re:Aw, come on ... by Anonymous Coward · · Score: 1

      One way it could come up is if the form data is serialized in CSV format (perhaps with an alternate delimiter such as vertical bar), and NULL is chosen as the text representation of a null. For example

      Alan,Smith,,M
      Jennifer,NULL,1990-12-03,F

      Alan refused to provide his birthdate and Jennifer apparently refused to provide her last name.

    4. Re:Aw, come on ... by Anonymous Coward · · Score: 0

      just the regular crap-tastic shit we've come to expect out of software because programmers have no professional association and anybody can call themselves a programmer after an hour of code. probably some dipshit trying to do their own parameter sanitizing.

      off the top of my head here's some c#. this is so fucking stupid i can't believe how often "programmers" manage to screw this up given how easy it is to just do fucking correctly in the first place.


      string surname = get_the_surname();
      SqlConnection dbh = get_db_connection_somehow_im_not_gonna_manage();

      sth = new SqlCommand("INSERT INTO Customer (Surname) VALUES (@surname)", dbh);
      sth.Parameters.Add(new SqlParameter("@surname", surname));
      sth.ExecuteNonQuery(); // don't forget to dbh.Close() at some point

      even works correctly if get_the_surname() returns null or when handling little bobby tables.

      these days i've been using java jpa (apache openjpa if anyone wants to know) so i rarely have to worry about sql unless i'm debugging something strange. not that i don't know sql, but i try to save that for stored procedures these days.


      String surname = get_the_surname();
      EntityManager em = get_entity_manager_somehow_im_not_gonna_manage();

      em.persist(new CustomerRecordDAO(surname)); // don't forget to em.getTransaction().commit() if necessary and do em.close() at some point

      i honestly don't understand how the fuckups we see daily in proprietary software including websites running in the clouds happen. there are clearly a whole lot of people running around calling themselves "programmers" like that ceo who thinks programming is copying and pasting from stackoverflow after merely translating some "jargon" who need to be prevented from calling themselves "programmers" until they learn what they fuck they're doing.

    5. Re:Aw, come on ... by bloodhawk · · Score: 1

      Possible, but highly unlikely to be a common problem then.

    6. Re:Aw, come on ... by gman003 · · Score: 1

      There's some app-tier logic that tends to fuck this up. I myself had to deal with it.

      In my case, I had written a set of webservices that took in parameters as POST form variables, and updated records accordingly. Parameters that were not sent were not modified. POST form variables are string-only, so I had originally planned for the empty string ("") to be the value indicating "set this field to null", but that caused problems for the web-tier developer, so (under mild protest) I made it so the string "null" would set a field to null.

      I had written it generically, and in such a way that it transformed the set-to-null string into an actual null prior to processing, so even fields which could not be set to null, like name fields, would be modified that way.

      And then there was a user named "Au Null".

      And then I forced the web-tier developer to figure out how to send an actual empty string.

      And then I used JSON forms for all future webservices, when I was given an option, so an actual null data type could be used.

    7. Re:Aw, come on ... by 93+Escort+Wagon · · Score: 2

      INSERT INTO Customer (Surname) VALUES ("NULL")

      Actually, I would hope that particular line would be more along the lines of

      INSERT INTO Customer (Surname) VALUES (?)

      --
      #DeleteChrome
    8. Re: Aw, come on ... by Anonymous Coward · · Score: 0

      I have yet to see a dataset get confused by "Null" and null. You have no idea what you're talking about.

    9. Re: Aw, come on ... by Anonymous Coward · · Score: 0

      Well put and my thoughts exactly. Unless some stupid ass is rolling their own SQL drivers, I can't see how they have this issue. Any SQL data I've ever used can clearly delineate between a string and a database directive.

    10. Re:Aw, come on ... by MichaelSmith · · Score: 1

      You execute the code, parse the output and assume any field with the value "null" is null.

    11. Re:Aw, come on ... by Anonymous Coward · · Score: 0

      decided to learn how to do this with libpqxx. example code if anyone's interested.


      pqxx::connection dbh("dbname=students");
      pqxx::work trans(dbh);

      trans.parameterized("INSERT INTO Students (student_name) VALUES ($1);")("Robert'); DROP TABLE Students; --").exec();

      trans.commit();

      ugh, my life is pathetic. it's a sunny day outside. i should be doing something else.

    12. Re:Aw, come on ... by MichaelSmith · · Score: 1

      Or format is address, first name, last name and the address is "2, 24 some street" and the last name is Jennifer.

    13. Re:Aw, come on ... by MichaelSmith · · Score: 1

      There is always that one developer who just knows that his SQL is 1.9 times as fast as the SQL used by frameworks, so he hard codes it.

    14. Re:Aw, come on ... by techdolphin · · Score: 1

      Shouldn't it be: INSERT INTO Customer (Surname) VALUES ("Null");

    15. Re:Aw, come on ... by MichaelSmith · · Score: 1

      If you must put "null" in a text field then put json in the text field.

    16. Re:Aw, come on ... by RabidReindeer · · Score: 1

      To the contrary. I run into it often. Not with names, but with people being sloppy about actual nulls versus entering "null" as a filler in a spreadsheet or something.

      Actually, to me a null in a database means that something's missing. I find using it to simply mean "blank value" as sloppy.

    17. Re:Aw, come on ... by Anonymous Coward · · Score: 0

      > implying modern languages have type

    18. Re:Aw, come on ... by KalvinB · · Score: 1

      What's happening is that the framework is converting the string "null" into the null value. Now that it came up that would also happen in my own PHP framework because it's a lot easier to convert the string "null" into the null value when generating queries in the ORM than to try to check for null values.

      If you handle "null" values you have the issue of setting things to null when what you intended was that those fields were not changed. If you use the string "null" then anything that has the value of null in the object is not updated in the database.

      There are other cases that also come up which incline you more to use the string "null" to indicate a null value should be stored in the database.

      I don't know what language or framework they're using but that's very likely the same general method they're using.

    19. Re:Aw, come on ... by The+MAZZTer · · Score: 1

      The name first has to pass through other layers even before it hits the database. I am betting it is getting hung up on JavaScript. Or to be more precise, poor JavaScript code (JavaScript itself is more than capable, it just is easier to make this kind of mistake if you're not careful).

      Specifically, if you manage to cast null to a string, you get "null". I can see someone casting everything to strings to compare them, making this mistake.

    20. Re:Aw, come on ... by hcs_$reboot · · Score: 1

      Maybe some dumb languages check for "null" (string) values. In PHP,
      echo "0" ? 1:0; // echoes 0
      echo "0.0" ? 1:0; // echoes 1

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    21. Re:Aw, come on ... by thegarbz · · Score: 1

      I find this hard to believe. If it were true then the applications involved would be open to worse exploits than simple SQL injection.

      This is what the future is all about. Once everyone knows how to code we don't need web forms and string parsing anymore. Anyone wanting to sign up to something should do it via SQL commands.

    22. Re:Aw, come on ... by Anonymous Coward · · Score: 0

      Easy.

      "empty string"

    23. Re:Aw, come on ... by AmiMoJo · · Score: 1

      Sometimes special strings are used as flags. A bit like how 9/9/99 was used as a "dummy record" date in some systems. All it would take is one key system somewhere, like a payment system, to specify that "NULL" is a special string used for test records or something and numerous down-stream apps would be forced to honour it.

      I agree, it does sound improbable, but not impossible. Like the guy whose name was "God" (eastern European, I forget from where exactly). You can imaging that would be some special keyword for creating a test account with access to all services.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    24. Re:Aw, come on ... by Anonymous Coward · · Score: 1

      yet apparently this is a real thing:

      http://stackoverflow.com/questions/4456438/how-do-i-correctly-pass-the-string-null-an-employees-proper-surname-to-a-so

    25. Re:Aw, come on ... by Anonymous Coward · · Score: 0

      perl -e 'print "null" eq null'
      1

    26. Re:Aw, come on ... by naranek · · Score: 1

      You just need some old legacy system, which has gone through a few iterations of modifications. There can be a number of ways you end up handling data without knowing the type. It doesn't need to be SQL Injection, it can be CSV import through some generic plugin or what ever. Suddenly you're stuck with strings that look like numbers, text, json, xml or who knows what. At that point it's possible to decide, that if the string is "null" you convert it to actual null and be done with it. The data importer might even try to guess data types for you (I'm looking at you Excel).

      Yeah, it's horrible and wrong and all that, but it still happens.

      --
      Only dumb birds land downwind.
    27. Re:Aw, come on ... by Anonymous Coward · · Score: 0

      One way it could come up is if the form data is serialized in CSV format (perhaps with an alternate delimiter such as vertical bar), and NULL is chosen as the text representation of a null. For example

      The point is that there IS NO text representation of a NULL value, and someone who tried to do that is why the code broke.

      Alan,Smith,,M
      Jennifer,NULL,1990-12-03,F

      Yes, Alan did not provide a birthdate, so a query should return an empty string or a NULL value, not the string "NULL".
      Someone probably half-assed some code somewhere and didn't understand how to return an error code, so they tried embedding it in the string itself.

    28. Re:Aw, come on ... by tibit · · Score: 1

      You really think that SQL injection isn't a thing, and that people all understand that SQL is a language with typed literals? The comparison to a 'NULL' or a "NULL" was a no-op, since it compares neither to a NULL value, nor to any of the names - until that one customer breaks your system. Sometimes it might not be such a bad idea to enforce condition coverage on stuff that affects all of your customers...

      --
      A successful API design takes a mixture of software design and pedagogy.
    29. Re:Aw, come on ... by Cro+Magnon · · Score: 1

      To me a "blank value" could be a space or a zero in a numeric field. Both of which are valid values (usually). A null shouldn't be a value, at least IMHO.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    30. Re:Aw, come on ... by Anonymous Coward · · Score: 0

      Many languages besides PHP are duck typed. That you don't seem to be aware of the concept says far more about you than about PHP.

    31. Re:Aw, come on ... by ncc74656 · · Score: 1

      First- and last-name fields in a database most likely should be set up as not null, as everybody has them. Middle initials (or middle names) are a bit more hit-or-miss and maybe should allow nulls. With this, your "Jennifer Null" example should be read into the database properly.

      (One of my pet peeves: database tables in which all fields allow nulls. That's almost as bad as a database with no relations defined between tables.)

      --
      20 January 2017: the End of an Error.
  9. Teh by MichaelSmith · · Score: 4, Funny

    An asian co-worker of mine who's family name is Teh has found that his name is almost impossible to type in tools like microsoft word, which auto correct Teh to The.

    1. Re:Teh by Anonymous Coward · · Score: 0

      Teh goggles...they do nothing!

    2. Re:Teh by Anonymous Coward · · Score: 0

      ... which auto correct Teh to The./quote

      He should be able to type CTRL-Z to undo the auto-correct and leave it as typed.

    3. Re:Teh by MichaelSmith · · Score: 1

      Yeah but I think it is more people sending documents to him which arrive as "Mr The". They don't even notice the autocorrect.

    4. Re:Teh by thegarbz · · Score: 1

      Not being able to type it in Word is just not knowing how to use Word. The Autocorrect options are very adjustable. Add the word to the dictionary and be done with it.

      Now as for every other piece of damn software out there such as Windows 10's built in autocorrect which affects all apps, that's not so easy.

    5. Re:Teh by Anonymous Coward · · Score: 0

      That's nothing. Then his countryman "Wot Teh Fuk" came along...

    6. Re:Teh by __aaclcg7560 · · Score: 1

      Early Microsoft Word spellcheckers almost always converted Clinton into Klingon (the word, not the language).

    7. Re:Teh by Anonymous Coward · · Score: 0

      MS Word's dictionary is too limited to be of much use for above-average work anyway. I had to use office when I began a science degree, and very quickly disabled anything remotely like autocorrect in every tool I had to touch for the fact the suites not only butchered scientific terms, but anything in which you wanted to use a vocabulary exceeding grade school--maybe middle school (if we want to be charitable).

    8. Re:Teh by Frosty+Piss · · Score: 1

      An asian co-worker of mine who's family name is Teh has found that his name is almost impossible to type in tools like microsoft word, which auto correct Teh to The.

      Failure to pay attention to "auto-correct" is a user error. Also, please not that with Word (and other word processors) this issue is handled by adding the word to your dictionary.

      This is *NOT* exclusively a Microsoft Word issue, but thanks for your Micro$loth prattle.

      --
      If you want news from today, you have to come back tomorrow.
    9. Re:Teh by stephanruby · · Score: 1

      An asian co-worker of mine who's family name is Teh has found that his name is almost impossible to type in tools like microsoft word, which auto correct Teh to The.

      In other words, your friend was just one google answer away from finding out how to add his name to a custom dictionary in Word.

    10. Re:Teh by MichaelSmith · · Score: 1

      Yeah he knows how to do that but all the other people typing his name (like at the power utility for example) have to learn it just for him.

    11. Re:Teh by AbRASiON · · Score: 1

      Oh dog! sometimes autocorrect is teh ducking worst :(

    12. Re:Teh by Tablizer · · Score: 1

      When Word first added auto-correct and nobody knew it was active, a lady's name, "Jina Brennan" was re-converted as "Jina Pregnant" because the typist at first typed the name in lower case. He/she corrected the capital, but not the name. HR went nuts.

    13. Re:Teh by Anonymous Coward · · Score: 0

      Except that's *not* how Word works. Autocorrect for "teh" is a separate function from the general spell checker and Word will continue autocorrect it whether or not it shows up with a red underline.

      But it's not like you stood up in public and tried to shame someone for not knowing how to do a thing that you yourself don't know how to do. Because that would mean.

    14. Re:Teh by Applehu+Akbar · · Score: 1

      "Bartender, pour me an African-American Modelo!"

    15. Re:Teh by MightyMartian · · Score: 1

      Can you imagine how hard a life the Pron family has!!!???

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    16. Re:Teh by MightyMartian · · Score: 2

      Well, don't blame me. I voted for Kodos!

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    17. Re:Teh by antdude · · Score: 1

      Same with (fir/1)st names. It is not just names, but lots of uncommon words esp(ecially) technical words. Hence, why I turn off auto(spell/correct).

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    18. Re:Teh by KGIII · · Score: 1

      I always treat them as if they need to be trained and then I do so accordingly. For example, I have a custom dictionary (actually several - for varied tasks/profiles) that has been curated for many, many years now. It's one of the first things I do when I set up a new system - I import my custom dictionary and overwrite the existing files where applicable. It's quasi-automated in the case of using a Live USB - I've a script that automates the retrieval of that file and a few others to put my profile into a standard configuration that is comfortable for me.

      --
      "So long and thanks for all the fish."
    19. Re:Teh by thegarbz · · Score: 0

      Except that's *not* how Word works. Autocorrect for "teh" is a separate function from the general spell checker and Word will continue autocorrect it whether or not it shows up with a red underline.

      But it's not like you stood up in public and tried to shame someone for not knowing how to do a thing that you yourself don't know how to do. Because that would mean.

      Did I say "general spell checker" anywhere in my post? The autocorrect dictionary is available in Options > Proofing > Autocorrect Options.

      Don't drink and post, it makes you look stupid.

    20. Re:Teh by Anonymous Coward · · Score: 0

      "My ancestors changed their family name when they arrived at Microsoft Word..."

    21. Re:Teh by Anonymous Coward · · Score: 0

      Blah. There's simply no excuse to have moronic defaults.

      Repeat that 1000 times.

      If I type in something, it's up to me to correct it, not some "smart" braindead algo.
      Take back your power.

    22. Re:Teh by Anonymous Coward · · Score: 0

      No, software elements that mistype what you just typed in are called "design flaws".
      If you must, provide a suggestion, but don't change what I wrote and require of me to catch it every damn time!
      Plus, it's stupid to hide your settings.

    23. Re:Teh by swb · · Score: 1

      IIRC, the Mac version of Word many years ago would spellcheck "childcare" as "kidnapping".

    24. Re:Teh by tinkerton · · Score: 1

      That's oddly appropriate. At least for Hillary.

    25. Re:Teh by shikaisi · · Score: 1

      Early Microsoft Word spellcheckers almost always converted Clinton into Klingon (the word, not the language).

      Perhaps they knew something we didn't.

      --
      No left turn unstoned.
    26. Re:Teh by cellocgw · · Score: 1

      Can you imagine how hard a life the Pron family has!!!???

      Let me guess, autocorrect changes the "o" to "0" (zero) ?

      (side note: Chrome catches "autocorrect" as misspelled. auto-correct not so much)

      --
      https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
    27. Re:Teh by Anonymous Coward · · Score: 0

      I had a co-worker who's first name was Teh. Yeah, that was fun. Fortunately they added the option to reverse the autocorrect.

    28. Re:Teh by Anonymous Coward · · Score: 0

      whose, not who is, genius.

    29. Re:Teh by kinko · · Score: 1

      Not being able to type it in Word is just not knowing how to use Word. The Autocorrect options are very adjustable. Add the word to the dictionary and be done with it.

      Now as for every other piece of damn software out there such as Windows 10's built in autocorrect which affects all apps, that's not so easy.

      I also work with someone whose family name is "Teh". The problem isn't him typing his own name into the computer, it's the entire rest of the world typing his name in. Eg I've seen conference proceedings and meeting minutes with his name spelled as "The".

    30. Re:Teh by Cro+Magnon · · Score: 1

      That's nothing. Then his countryman "Wot Teh Fuk" came along...

      Damn, wish I hadn't blown my modpoints! :)

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    31. Re:Teh by david_thornley · · Score: 1

      So you're saying that all we need to solve this problem is perfect users?

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  10. "Null" doesn't surprise me at all by Anonymous Coward · · Score: 0

    I work with an intelligent and pretty good engineer who designed a REST API where he would treat query parameters such as "foo=null" as assigning null to foo and not "null". It took quite a lot to convince him that we was wrong. I'm sure this mistake is made all the time.

  11. I can't book an airline ticket by Anonymous Coward · · Score: 0

    I get to the checkout page, hit submit and it says "Missing required field". Good thing I have my own plane!

    - Cher

    1. Re:I can't book an airline ticket by MichaelSmith · · Score: 1

      Hope the registration of your plane isn't FPL because thats part of the syntax of an ICAO flight plan creation message.

    2. Re:I can't book an airline ticket by Anonymous Coward · · Score: 0

      Forget flying, you should get around exclusively by skiing. It's a shame the world can't kill that copyright-whore husband of yours twice, but if you smack into an errant tree we'll call it even.

    3. Re:I can't book an airline ticket by hcs_$reboot · · Score: 1

      Cher is not allowed to fly, her tight skin may not withstand high altitude air pressure.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
  12. I solved the problem with my long complicated name by Anonymous Coward · · Score: 0

    ...by simplifying it.

    Use one short first name and one short surname, or suffer for your insufferable ego.

  13. McKenzie should just get a Japanese name by Anonymous Coward · · Score: 0

    It's unreasonable to expect the Japanese to change their systems because of a problem that only occurs for badly integrated foreigners.

    1. Re:McKenzie should just get a Japanese name by 93+Escort+Wagon · · Score: 1

      It's unreasonable to expect the Japanese to change their systems because of a problem that only occurs for badly integrated foreigners.

      Doesn't Japan actually require immigrants to adopt a Japanese name?

      --
      #DeleteChrome
    2. Re:McKenzie should just get a Japanese name by xlsior · · Score: 1

      Doesn't Japan actually require immigrants to adopt a Japanese name?

      Even if they would, what about visitors/tourists/international customers?

    3. Re: McKenzie should just get a Japanese name by RightwingNutjob · · Score: 1

      Easy answer: the Japonese should speak English and write with Latin characters like civilized people have done since time immemorial.

    4. Re:McKenzie should just get a Japanese name by hcs_$reboot · · Score: 1

      Certainly not. Foreigner names may be "translated" into the katakana alphabet, which doesn't change much the number of characters (since full width katakana take each 2 bytes). Some foreigners get themselves a name in "kanji" (ideograms), but that name (unless it's the spouse name) has not official value.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    5. Re: McKenzie should just get a Japanese name by hcs_$reboot · · Score: 1

      Like most cultures/countries - the Japanese are deeply attached to their cultural roots and want to preserve their language/alphabets/kanji.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    6. Re:McKenzie should just get a Japanese name by Anonymous Coward · · Score: 0

      I don't think so. When I was living in Japan for a while and opened a bank account, I had to write down my name in Roman and then say my name out loud a bunch of times so that the bank clerk could write down a passable version in their katakana script. This made sense, since they aim for something that sounds roughly correct, and there is no straight way to convert from Roman to Japanese scripts, as pronounciation varies greatly for the many languages using Roman script.

      As for 'impossible' names: I was called back to the bank a few days later as my (European) name in Roman was way too long for their electronic name field. Some parts of my name had to be omitted and they wanted me to indicate which bits were not so important.

      My bank card had both the simplified Roman and katakana version of my name on it.

    7. Re:McKenzie should just get a Japanese name by Anonymous Coward · · Score: 0

      Doesn't Japan actually require immigrants to adopt a Japanese name?

      No, you don't have to change your name if you move to Japan, but if it contains characters that are neither Latin nor Japanese (e.g. Devanagari characters), then you will have to transliterate it either into Latin characters or katakana.

      If you naturalise, then you have to take a Japanese name, i.e. you have to use the same rules that Japanese parents have to follow when naming their children. You could go for a full Japanese name, or use your existing name in katakana, or something in between. But naturalisation is fairly rare for foreigners in Japan, mostly because you have to give up your original nationality.

    8. Re:McKenzie should just get a Japanese name by Anonymous Coward · · Score: 0

      Doesn't Japan actually require immigrants to adopt a Japanese name?

      Japan does not require that.

  14. Last name cannot be left Blank by bitflusher · · Score: 2

    My uncle experienced this problem with our last name: Blank. When filling out a form it returned with an error: Last name cannot be left blank. This is still a running joke in our family. Never experienced it myself.

    1. Re: Last name cannot be left Blank by Anonymous Coward · · Score: 0

      I think your uncle was telling a joke

  15. LoL by meerling · · Score: 0

    The problem is stupid programmers, or script monkeys, that make really bad assumptions or restrictions.
    It's not that hard to avoid these issues in the first place, unless you're working on a system that only has 256 bytes.
    Yes, I learned machine language on computers that literally only had 256 bytes.
    I'm definitely using the right term of byte, as in a group of 8 bits, each bit being a representation of a 1 or a 0.
    I know your phone 'may' literally have a billion times more memory/storage, but it's not always that convenient.

    1. Re:LoL by bugs2squash · · Score: 2

      I don't think a byte has always been 8 bits, so there's definitely some wiggle room there as long as the bits are contiguous.

      --
      Nullius in verba
    2. Re:LoL by Megol · · Score: 3, Informative

      Byte size have varied a lot in the past and could conceivably vary in the future too (but it's unlikely). Even the definition of byte as a concept have varied, most have byte as the smallest addressable element while some systems had it as the character size etc. Word addressed machines very seldom used byte to describe the addressable element size but some had word-sized characters... It's a mess.

      A more correct name is octet which by definition consists of 8 binary digits.

    3. Re:LoL by serviscope_minor · · Score: 2

      Yes, I learned machine language on computers that literally only had 256 bytes.

      I wrote a new course to teach students on a machine with only 64 bytes of RAM (1k word ROM and 128 bytes EEPROM) . In 2008 or so. Such machines still exist in staggeringly huge numbers. See, for example the PIC12F675. Their bottom end model (the 10F200) has a staggering 16 bytes of RAM and 256 words of flash.

      So I'm guessing you're either an ancient greybeard or did a machine language course on a very small microcontroller.

      I did like the super low-end microcontrollers for teaching. One thing I found appealing was it was the first bit of the engineering course (and it happened early) when the students can step outside of the slightly artificial uni environment and into the real world. I mean sure there are all sorts of strange restrictions on a PIC, but importantly, they're all there for a reason and that reason is never to make it simpler for teaching. And most of the answers to "why does it do this weird thing" were "well, that saves a couple of transistors which lowers the cost", but it was nice to work with a solid product which was engineered to some very strict criteria.

      And the devices are simple enough that you can give the students the 400 page databook and the answers will be in there somewhere.

      --
      SJW n. One who posts facts.
  16. And then there's filters... by jeffasselin · · Score: 3, Funny

    I've had issues a few times with filters on names rejecting mine for supposedly referring to a body part...

    --
    If he explores all forms and substances Straight homeward to their symbol-essences; He shall not die.
    1. Re:And then there's filters... by blindseer · · Score: 4, Funny

      I heard a story from a college friend of mine about someone in his family, his dad I think, getting in some trouble while drinking with some Army buddies. So these three friends go out and have a few too many and are picked up by the local police for public intoxication or something similar. The cop asked for their names. They replied in turn, Dicks, Cox, and Bahl (pronounced like "ball"). The cop thought they were trying to be funny. They were hauled off to the station and were only released after the First Sergeant showed up to verify their names.

      --
      I am armed because I am free. I am free because I am armed.
    2. Re:And then there's filters... by rgmoore · · Score: 2

      This is a common enough event that it has a name: The Scunthorpe Problem. Naive spam blockers are a pox on the internet.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    3. Re:And then there's filters... by Tablizer · · Score: 1

      Why would that happen, Mr. Selin?

    4. Re:And then there's filters... by Anonymous Coward · · Score: 0

      I'm guessing you're just going for the +1 Funny, but it wouldn't surprise me that army plebs would forget to have ID since they're generally not very strong in the brain box.

    5. Re:And then there's filters... by blindseer · · Score: 1

      Point is that this is an old problem that predates computers. Some basic "sanity checks" on data input can fail even with a human parsing the data.

      Also, fake identity cards are not a new phenomenon either. I do not recall if the soldiers out on the town had ID or not. Presumably they were in uniform and/or produced military ID prompting the call to the First Sergeant rather than checking with some other authority to verify ID.

      --
      I am armed because I am free. I am free because I am armed.
    6. Re:And then there's filters... by Anonymous Coward · · Score: 1

      There was an art historian working in Poland named (after translating his name to English) Sigmund King. He got promoted to work in a castle -- a residence of polish monarchy called Wawel, situated in an old capital of Poland -- Cracow. Official snail-mail sent to him notoriously couldn't reach him, because it was usually addressed to King Sigmund, Wawel, Cracow. The post office usually thought this was a joke mail to a real dead king, returned it with a note saying "the addressee is long deceased".

    7. Re:And then there's filters... by chooks · · Score: 1
      --
      -- The Genesis project? What's that?
    8. Re:And then there's filters... by Anonymous Coward · · Score: 0

      Worked with a German guy who's last name was Fox. In German. F-U-C-H-S. He said people were always laughing when he told them how to spell it.

    9. Re:And then there's filters... by trojjan · · Score: 1

      From bash.org:
      <Tom> i put my username in as tom pocock, and when they sent me the confirmation email, my login name is Tom PoMrWinky

    10. Re:And then there's filters... by Anonymous Coward · · Score: 0

      And our former Speaker of the House (Boehner) may have run into a problem in school with the proper pronunciation of his surname ("boner")... Still, given the spelling indicating the German origin of the name, even anglicized, I fail to see how it could possibly be distorted to "bay-ner"... Someone in his family probably should have changed the spelling?

    11. Re:And then there's filters... by Cro+Magnon · · Score: 1

      Not as bad as yours, but I've seen the name Richard Head. Except that he used the abbreviation for Richard. Really, I don't know why ANY Richard would use that abbreviation, but especially not with that last name.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  17. Had a student in a DB class - last name "Long" by ohieaux · · Score: 1

    I could never create his account (last name as ID). It took me some time to realize the parser was picking up on the keyword long. It was decades ago, so I expected things like that were fixed.

    --
    Where all think alike, no one thinks very much.
    1. Re:Had a student in a DB class - last name "Long" by Megane · · Score: 1

      It was decades ago, so I expected things like that were fixed.

      They're probably double now. Most people stopped using fixed a long long time ago.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  18. First world problem by Anonymous Coward · · Score: 0

    Your name crashed a computer while blacks in Africa are looking for some food to nibble on.

  19. Way too long of a name with tragic consequences by Anonymous Coward · · Score: 0

    My friend Eddie Cucha Catcha Camma Toe-Sa Nara Toe-Sa Nocka Samma Camma Wacky Brown fell into the well. The 911 system couldn't handle his name and he drowned. I wanted to put his name in the comment subject, but it was too long to fit

  20. Now who is laughing at Iceland? by 140Mandak262Jamuna · · Score: 1
    Iceland does not allow babies to be named in a way that does not conjugate correctly in Icelandic for all the case endings. And when the new story broke it caused much mirth and amusement among the "land of the free" who bragged about their freedom to be named Lakshumanan Satyavakeeswaran or Venkatachalapathy Ramanujadasan Seshadrinadhan Kodandaraman Aiyengar. Now, who is laughing?

    It is high time the government refuses to register any name that is not Unicode compliant, within so many bytes with some reserved names that are not allowed. No more onefortymandaktwosixtwojamuna to you.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    1. Re:Now who is laughing at Iceland? by RightwingNutjob · · Score: 1

      Unicode? Fuck no. Latin characters abcdefghijklmnopqrstuvwxyz. No spaces, no apostrophes, no arbitrary puncutation marks, and no fucking emojis, non-fucking emojis, or any emojis at all.

    2. Re:Now who is laughing at Iceland? by Teun · · Score: 1

      Since 1968 ASCII all the way!
      If a redneck can't read it must be un-American

      You honour you're nick :)

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    3. Re:Now who is laughing at Iceland? by Anonymous Coward · · Score: 0

      Unicode? Fuck no. Latin characters abcdefghijklmnopqrstuvwxyz. No spaces, no apostrophes, no arbitrary puncutation marks, and no fucking emojis, non-fucking emojis, or any emojis at all.

    4. Re:Now who is laughing at Iceland? by serviscope_minor · · Score: 1

      Unicode? Fuck no. Latin characters abcdefghijklmnopqrstuvwxyz. No spaces, no apostrophes, no arbitrary puncutation marks, and no fucking emojis, non-fucking emojis, or any emojis at all.

      I think that's pretty unfair. Mr. U+1F4A9 has a hard enough life already without you stopping him from using online services.

      --
      SJW n. One who posts facts.
  21. Ridiculous Premise by BoFo · · Score: 4, Insightful

    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.

    1. Re:Ridiculous Premise by wonkey_monkey · · Score: 1

      Data cannot break computers.

      Why not? Kirk used to do it just by talking to 'em.

      --
      systemd is Roko's Basilisk.
    2. Re:Ridiculous Premise by serviscope_minor · · Score: 1

      Data cannot break computers.

      Pray you never encounter the Death Byte.

      --
      SJW n. One who posts facts.
    3. Re:Ridiculous Premise by Keybounce · · Score: 1

      Data cannot break computers.

      I'd say that Data's strength was more than enough to break computers.

      Now, if you mean the concept of information expressed in a representable manner, I would point out that computers have to do work to do anything more than copy that data; and as soon as you have to manipulate the data, it can manipulate you back.

      ... I'm not doing a good job of describing this, sorry.

      In some sense: any finite system that wants to operate on unknown data will have some case where the data fails to match the expectation. See "Music to break record players by" in "Godel Escher Bach", and similar issues.

    4. Re:Ridiculous Premise by Anonymous Coward · · Score: 0

      While we're on this topic, can I just ask folks not to put "[none]" or "xxxxx" or "-----" or anything else in blank fields. OK? Thanks.

    5. Re:Ridiculous Premise by Anonymous Coward · · Score: 0

      Data cannot break computers.

      sure it can: https://en.wikipedia.org/wiki/Killer_poke

  22. name to short by Anonymous Coward · · Score: 0

    Its standard practice in a lot of places to use first initial and first three letters of last name as the basis of a user ID.
    This is a problem for a guy i know his last name is `Ey`

    1. Re:name to short by TroII · · Score: 0

      At one company where I've worked, we had some horrid abomination of an intranet web application that performed all sorts of stupid arbitrary checks like this. The intranet was utilised to add all new hires into all of our systems: intranet account, email, HR, travel system, calendar, helpdesk, yadda yadda. They'd fill out a form with the person's info and the intranet web app would automagically populate all of the other databases and set up all the varied accounts. Great thing, when it worked, which was 99.9% of the time, a real timesaver.

      One of the requirements, for some inexplicable reason lost to the inevitable passing of institutional knowledge, was first names had to be at least 2 chars. Well one day we got an employee whose real given name was 25+ characters long, Tavarithpindarthaseeramanjian or something, and when he naturalized to the US he changed his legal first name to "T" - just the letter. The lady who did employee onboarding dutifully filled out the intranet form and of course it bombed out on the two character requirement. Her trouble ticket went to the developer team responsible for the intranet, who kicked it over to me as the DBA saying the character requirement was not easily changed (WTF?). When I looked around at how many systems I was going to have to manually add this guy to - I instructed the onboarding lady to enter his first name as "Mr. T" instead, and the form would work.

      And that's the story of how that company wound up with a rather short and slight looking, completely unimposing Indian guy who was known company wide as "Mr. T"...

  23. unicode by bugs2squash · · Score: 1

    Try typing Björn into a lot of web site name fields. I'm not sure that slashdot should be too vocal on this, I don't think the umlauts would have shown up until recently.

    --
    Nullius in verba
    1. Re:unicode by Zontar+The+Mindless · · Score: 1

      Slashdot has always supported at least Latin-1, which includes umlauts. Although there was a brief period of time when you had to write them as HTML entities.

      Slashdot supported Unicode for a while, but support for anything beyond Latin-1 was later disabled due to the antics of page-widening trolls and such. Why reach for a newspaper to swat that fly when you can grab a sledgehammer instead?

      --
      Il n'y a pas de Planet B.
  24. Programers can not even figures by Anon-Admin · · Score: 3, Interesting

    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.

    1. Re:Programers can not even figures by Anonymous Coward · · Score: 3, Insightful

      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.

    2. Re:Programers can not even figures by 93+Escort+Wagon · · Score: 2

      You're gonna have to let us know just how many "test" emails you receive in the next few days!

      --
      #DeleteChrome
    3. Re:Programers can not even figures by StormReaver · · Score: 3, Insightful

      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.

    4. Re:Programers can not even figures by Anonymous Coward · · Score: 0

      Because the spec for email address is is ridiculously complex.

      The spec for email addresses is given in ABNF, which can be trivially translated to code in any half-decent parsing framework.

    5. Re: Programers can not even figures by Hardhead_7 · · Score: 1

      I've had this issue with Irish email addresses. Several of our customers are in Ireland and have an email like seano'connor@foo.com, which is a valid address, but a library I was using rejected it.

    6. Re:Programers can not even figures by Hunter-Killer · · Score: 1

      Hello fellow victim of RFC 3696:

      Without quotes, local-parts may consist of any combination of alphabetic characters, digits, or any of the special characters

                  ! # $ % & ' * + - / = ? ^ _ ` . { | } ~

      period (".") may also appear, but may not be used to start or end the local part, nor may two or more consecutive periods appear.

      The wording isn't grammatically correct. There's two interpretations:

      local-parts may consist of any combination of alphabetic characters, digits, or any of the special characters [including period] may also appear, but may not be used to start or end the local part

      --or--

      Sentence 1: Without quotes, local-parts may consist of any combination of alphabetic characters, digits, or any of the special characters [special characters follow].
      Sentence 2: Period (".") may also appear, but may not be used to start or end the local part, nor may two or more consecutive periods appear.

      The first applies the ending character restriction to all special characters, while the second only to period.

    7. Re:Programers can not even figures by RuffMasterD · · Score: 1

      The specs are remarkably flexible, but sites add their own rules, different for each site of course.

      One thing the specs DO NOT allow is for consecutive decimals (..) in the username. Sure enough, one customer sent me a list of email addresses, some of which had consecutive decimals. I tell them it's contrary to the RFC. They reply that the emails are correct. My mail relay rejects those addresses, as it should. I would like to know what mail relay they ran, and if those users ever received emails from external sources.

      --
      Human Rights, Article 12: Freedom from Interference with Privacy, Family, Home and Correspondence
    8. Re:Programers can not even figures by Anonymous Coward · · Score: 0

      http://www.ex-parrot.com/pdw/Mail-RFC822-Address.html

    9. Re:Programers can not even figures by Anonymous Coward · · Score: 0

      Filter error: Please use fewer 'junk' characters.
      http://www.ex-parrot.com/pdw/M...

    10. Re:Programers can not even figures by Ly4 · · Score: 1

      My pet peeve: web sites that can't handle Gmail's '+' addresses, but don't actually flag it as an error. Instead, they go off into la-la land.

      It's usually an indication that someone screwed up the quoting somewhere along the way (and obviously they missed a bit with their testing ,too).

    11. Re:Programers can not even figures by Anonymous Coward · · Score: 0

      No, the first interpretation is not what it could mean, gramatically. It could mean that if it were "...digits; any of the special characters ... or period (".") may also appear" but it does not say that. In contemporary English the RFC unequivocally states that the only specially non-terminating char is the period. It can be (and has been) misread, though.

    12. Re:Programers can not even figures by hcs_$reboot · · Score: 1

      The domain doesn't resolve, even the MX type.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    13. Re:Programers can not even figures by Actually,+I+do+RTFA · · Score: 1

      He's hoping a lot. That address was specifically set up to gather live e-mail addresses for spamming. Email addresses for technical people, so obviously the spam will be about new languages and articles by that Branson? guy who used to use the /. frontpage as his personal blog..

      --
      Your ad here. Ask me how!
    14. Re:Programers can not even figures by Anonymous Coward · · Score: 0

      I have to agree. Assumptions like "all people have names" or "you can't have more than 64 characters in a name" will be wrong, but not only can it be a very small percent of the time, but addressing these edge cases is actually difficult. Unsanitized inputs or accepting data as meta-data like "null", as well as blocking valid characters, are just flat fucking stupid.

    15. Re:Programers can not even figures by Actually,+I+do+RTFA · · Score: 1

      True, but a maximum number of characters for a name is perfectly fine.

      --
      Your ad here. Ask me how!
    16. Re:Programers can not even figures by Rockoon · · Score: 1

      There is a good excuse. The excuse is that there really isnt a good solution.

      All solutions are variations on a theme, altering the rate, but not eliminating the possibility, of choking.

      --
      "His name was James Damore."
    17. Re: Programers can not even figures by Anonymous Coward · · Score: 0

      That's nice. Was there supposed to be a point?

    18. Re: Programers can not even figures by Anonymous Coward · · Score: 0

      That's "informational". People should be using the property standards, which include unambiguous ABNF.

    19. Re: Programers can not even figures by jellomizer · · Score: 1

      One thing I never got about Most SQL databases is the use of the single quote as its primary string deliminator. Storing names is an extremely common tasks and names like O'Connor are often cause problems...
      However it could be stated that because of that it forces people to clean their syntax earlier in the process to prevent SQL injection. Unless the software producer gets lazy and say no special characters.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    20. Re:Programers can not even figures by Anonymous Coward · · Score: 0

      How ass backwards. Programs comply to specifications. If specifications are not the same as the program, the developer is at fault. We are supposed to be smart. Complex shouldn't be a problem. Be a professional.

      If you can't comply with a spec then you are an incompetent programmer. Simple as that.

    21. Re:Programers can not even figures by Keybounce · · Score: 1

      Actually, how about letting me include the final "." at the end of my domain name, after the ".com"?

      I grew up, at UCLA, learning all about early problems with the DNS system because when that final dot was not included, a mis-configured system would have all sorts of issues.

      Or did you realize that there are names like ".com.edu", ".com.com", ".edu.com", and ".edu.edu" out there?

    22. Re:Programers can not even figures by stub667 · · Score: 1

      It may be valid according to the RFC, but programmers quickly learn to ignore that due to all the systems that don't cope with the RFC. It is better to not accept it at input time than deal with all the problems you are going to get later from relays, proxies, all your own software, all the 3rd party software you need to integrate with, and all the mail clients that need to be used to contact you. It gets tiring, so we say alphanumeric only and stop being a smart alec. We have enough trouble dealing with IDNA and new TLDs without dealing with 'the programmer formerly known as Anon-Admin'.

    23. Re:Programers can not even figures by Anon-Admin · · Score: 1

      None so far, most people dont know the difference between the domain and a host address on the domain.

      As is obvious from someone who posts later saying that it does not resolve an MX record. lol

      As to the person who responded that it was harvesting email address. Spammers have much easier ways to collect email. There business is bulk, Bulk addresses and bulk mailings, it would be a waist of time for them to try to decode one address and an even bigger waist to expect others to decode an address and email it.

      Besides, if someone does spam the address it just adds more patterns to my bayesian spam filter. ;)

    24. Re:Programers can not even figures by Anonymous Coward · · Score: 0

      And programmers in general get paid the big bucks to figure out complex standards, algorithms and code. Not an excuse.

    25. Re:Programers can not even figures by suutar · · Score: 1

      I agree that it's not grammatically correct, but the first interpretation is so much more painfully ungrammatical that I feel forced to assume the second interpretation is the intended one until I see some real evidence otherwise.

    26. Re:Programers can not even figures by StormReaver · · Score: 1

      Because the spec for email address is is ridiculously complex.

      Having written a host name and domain name validator from RFC's, I have to disagree. The specifications are fairly simple and straight forward. Very detailed, but fairly simple.

  25. not sure I believe story by bloodhawk · · Score: 1

    Story sounds suspicious. Null as a string is not a reserved word or a name that should cause problems unless they are doing some really weird shit. You might check a string for being NULL but you would never check a string to see if it was equal to "Null" (unless you are employing retard programmers).

    1. Re:not sure I believe story by radarskiy · · Score: 1

      "unless you are employing retard programmers"

      You don't believe this part could happen?

    2. Re:not sure I believe story by dbIII · · Score: 1

      More parsers than you would think really suck so fall deep into the category of "really weird shit". There's one I've had the misfortune of dealing with where if users insert an apostrophe into a comment the application attempts to execute everything after that in a shell. The wonders of closed source software - delivering such a blatant security hole from at least 1998 until today.

    3. Re:not sure I believe story by Anonymous Coward · · Score: 0

      "unless you are employing retard programmers"

      You don't believe this part could happen?

      No way! Our H-1B workers are too qualified to fall for such nonsense.

    4. Re:not sure I believe story by Rockoon · · Score: 1

      ..and if the communication channel between two application layers is a single string containing all parameters... how do you encode null parameters?

      --
      "His name was James Damore."
    5. Re:not sure I believe story by Tony+Isaac · · Score: 1

      I've seen programmers get into the habit of using SQL like this:

      If IsNull(LastName, 'NULL') = 'NULL' Then RaiseError...

      Even SQL Server Management Studio allows you to enter a string "NULL" in a field, which it converts to a NULL value.

  26. Remember the TREATY OF HUDAIBIYAH by 140Mandak262Jamuna · · Score: 1
    The treaty of Hudaibuyah" is famous for the reason given for its abrogation. Mohammad claimed the treaty signed when had been weak was no longer enforceable, once he became strong.

    All the names people gave themselves when we database programmers were weak is no longer enforceable once we became strong. Now we enter the name of the baby at birth in the hospital. If the name could not be entered, tough luck, pick a new name proud parents! Not born in a hospital? Hospital does not have computer? tough luck, no social security number to your baby, no way to do anything in US of A. We are the dbase programmers, we rule the world.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  27. stupid swear filters by DaEMoN128 · · Score: 1

    My last name tripps up decency filters on websites. My wife tried to create an account on some website and it wouldnt accept our last name in the registration field saying foul language wasn't allowed.

    My last name.. Dike

    --
    Stop signs are only Suggestions
    1. Re:stupid swear filters by Applehu+Akbar · · Score: 1

      Be glad you're not the geologist who has to get a paper on intrusion dikes past the campus censorship system.

    2. Re:stupid swear filters by DaEMoN128 · · Score: 1

      actually, I do sign paperwork A. Dike just to get reactions (first initial, last name). Love it when I have to put my name on the board. I do this just to get a reatction out of the youngens in my class.. I'm mid 30's and going back to school for the fun of it :D

      --
      Stop signs are only Suggestions
    3. Re:stupid swear filters by Cro+Magnon · · Score: 1

      He probably predated computers, but there was an actor who would have fun with such systems. Dick Van Dyke.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    4. Re:stupid swear filters by Anonymous Coward · · Score: 0

      he only died a few years ago. I bet he'd have issues with multiple things, 1st being the space in his name in some systems, (remove the space and vandyke probably isnt an issue), and if it did allow the space, the Dyke would definitely cause problems.

    5. Re:stupid swear filters by Cro+Magnon · · Score: 1

      he only died a few years ago. I bet he'd have issues with multiple things, 1st being the space in his name in some systems, (remove the space and vandyke probably isnt an issue), and if it did allow the space, the Dyke would definitely cause problems.

      I'd forgotten about the space issue. One of my former cow-orkers was named "Van Kirk" and I remember him complaining about systems that choked on his space, or printed it without the space.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    6. Re:stupid swear filters by Anonymous Coward · · Score: 0

      > he only died a few years ago.

      Check again.

  28. Not just names by MPAB · · Score: 1

    It happened to me in Spain. Foreigners get IDs that start with an X, while natives' IDs start with a 0. There was this system to get the payroll ant it wouldn't accept an ID if it didn't start with a 0. The IT zombies tried to convince me once and again that I was inserting my password incorrectly as the illiterate "sudaka" I obviously was. It wasn't till I used technical jargon and told them to log on using the VNC that they took me seriously and fixed it.

    1. Re: Not just names by MPAB · · Score: 1

      Before someone beats me to it: It's "payroll and..." not "payroll ant..."

  29. Shit coders by JustAnotherOldGuy · · Score: 1

    Sorry, but if a last name of "Null" breaks your code, you're a shit coder.

    The same for name fields- a 50 character limit should be the minimum. Database space is cheap, what exactly do people think they're saving by restricting a name field to 20 characters or so?

    It pisses me off when a site insists that your last name HAS to be more than 2 characters, or that your first name can't be a single letter. Believe it or not, some people DO have names like that. If he was still alive someone like e. e. cummings wouldn't be able to sign up for jack shit these days because most sites insist that a period simply cannot be a part of your name, and a one-letter name is somehow illegal.

    It makes sense to restrict some fields to some maximum value when the upper limit is known (i.e. phone numbers, zip codes, US state names, etc) but for any arbitrary data it makes no sense to enforce an unrealistic maximum. Yes, most last names are less than 30 characters, but not all are. Why would you put in some stupid hard max limit like 30 characters?

    Seriously, what the fuck does it cost you to define a column as 100 chars wide instead of 30? What benefit are you supposedly gaining by restricting it to 30 chars? Are you being charged by the letter or something? Sure, a 100 character limit seems unduly generous, but the moment a customer can't create an account because of your mindless stinginess, you're the one that loses a sale, not them.

    I've been coding for decades and it's both gratifying and disheartening to see so many large, well-funded companies making these idiot-level mistakes that I don't make. I have a hard time believing that I'm smarter than all the coders at some of these large companies, but the evidence seems to show I am, at least in some areas.

    --
    Just cruising through this digital world at 33 1/3 rpm...
    1. Re:Shit coders by Anonymous Coward · · Score: 0

      VARCHAR255 is the default for all strings in all my database schemas.
      It costs 1 extra byte in theory, but in practice it saves space because it's not reserving 255 characters it's saying it can be between 0 & 255 characters long and IIRC it just uses a bog standard null terminated string. Where as CHAR30 uses 30 characters regardless of whether or not 30 were inserted. It will null pad. Right?

    2. Re:Shit coders by Anonymous Coward · · Score: 1

      Reminds me of something I read a while ago about names:
      http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/

      All of these assumptions are wrong. Try to make less of them next time you write a system which touches names.

      People have exactly one canonical full name.
      People have exactly one full name which they go by.
      People have, at this point in time, exactly one canonical full name.
      People have, at this point in time, one full name which they go by.
      People have exactly N names, for any value of N.
      People’s names fit within a certain defined amount of space.
      People’s names do not change.
      People’s names change, but only at a certain enumerated set of events.
      People’s names are written in ASCII.
      People’s names are written in any single character set.
      People’s names are all mapped in Unicode code points.
      People’s names are case sensitive.
      People’s names are case insensitive.
      People’s names sometimes have prefixes or suffixes, but you can safely ignore those.
      People’s names do not contain numbers.
      People’s names are not written in ALL CAPS.
      People’s names are not written in all lower case letters.
      People’s names have an order to them. Picking any ordering scheme will automatically result in consistent ordering among all systems, as long as both use the same ordering scheme for the same name.
      People’s first names and last names are, by necessity, different.
      People have last names, family names, or anything else which is shared by folks recognized as their relatives.
      People’s names are globally unique.
      People’s names are almost globally unique.
      Alright alright but surely people’s names are diverse enough such that no million people share the same name.
      My system will never have to deal with names from China.
      Or Japan.
      Or Korea.
      Or Ireland, the United Kingdom, the United States, Spain, Mexico, Brazil, Peru, Russia, Sweden, Botswana, South Africa, Trinidad, Haiti, France, or the Klingon Empire, all of which have “weird” naming schemes in common use.
      That Klingon Empire thing was a joke, right?
      Confound your cultural relativism! People in my society, at least, agree on one commonly accepted standard for names.
      There exists an algorithm which transforms names and can be reversed losslessly. (Yes, yes, you can do it if your algorithm returns the input. You get a gold star.)
      I can safely assume that this dictionary of bad words contains no people’s names in it.
      People’s names are assigned at birth.
      OK, maybe not at birth, but at least pretty close to birth.
      Alright, alright, within a year or so of birth.
      Five years?
      You’re kidding me, right?
      Two different systems containing data about the same person will use the same name for that person.
      Tw

    3. Re:Shit coders by Anonymous Coward · · Score: 0

      Erm Edward Estlin Cummings to you

    4. Re:Shit coders by JustAnotherOldGuy · · Score: 1

      You're absolutely right, and I don't know why your comment was downvoted to 0.

      Yes, I usually either use the default VARCHAR or 255; sometimes I limit it, but never down to something like 30 for a name.

      --
      Just cruising through this digital world at 33 1/3 rpm...
    5. Re:Shit coders by JustAnotherOldGuy · · Score: 1

      Erm Edward Estlin Cummings to you

      He went by e. e. cummings and I respect his wishes.

      His wife once said that he would "spend all morning putting in a comma", and then, "spend all afternoon taking it out".

      I like to think that's true.

      --
      Just cruising through this digital world at 33 1/3 rpm...
    6. Re:Shit coders by serviscope_minor · · Score: 1

      Sorry, but if a last name of "Null" breaks your code, you're a shit coder.

      Yep.

      No disagreement there.

      --
      SJW n. One who posts facts.
    7. Re:Shit coders by Anonymous Coward · · Score: 0

      Why would have Edward Estlin Cummings have any problems with 'single letter' / 'contains a period' names?

    8. Re:Shit coders by pjt33 · · Score: 1

      This seems to be more reliably attributed to Oscar Wilde.

    9. Re:Shit coders by JustAnotherOldGuy · · Score: 1

      This seems to be more reliably attributed to Oscar Wilde.

      "Don't believe everything you read on the internet." -- Abraham Lincoln

      --
      Just cruising through this digital world at 33 1/3 rpm...
    10. Re:Shit coders by painandgreed · · Score: 1

      Sorry, but if a last name of "Null" breaks your code, you're a shit coder.

      The same for name fields- a 50 character limit should be the minimum. Database space is cheap, what exactly do people think they're saving by restricting a name field to 20 characters or so?

      True, but in my experience, those customer facing interfaces are dependent on God knows how many downstream systems. All it takes in one to have a bad coder or some other restriction to force everything upstream to adhere to it also. Get several that have different such issues and things get silly. At my work, passwords require a symbol, however all the systems that use that password have different restrictions, so that there are only four symbols that are possible to use that will work in all the systems. Thus we have to enforce those restrictions when the user creates their passwords.

    11. Re:Shit coders by neminem · · Score: 1

      I dunno about that, but I bet he would've faced a lot of Scunthorpe problems, anyway.

  30. Could be worse... by Sooner+Boomer · · Score: 1

    Your name could be Cherry Chevapravatdumrong. She's one of the producers on Family Guy.
    http://www.imdb.com/name/nm221...

    --
    Chaos maximizes locally around me.
  31. The fancy-pants name for this problem by istartedi · · Score: 1

    The fancy-pants name for this is the semipredicate problem

    I don't recall how I stumbled upon that article; but it's one of my favorite "look at me, I can use a long word for it" things now.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  32. They forgot about Wolfe+585 by psychonaut · · Score: 2

    The article neglects to mention perhaps the most famous case of all, Hubert Blaine Wolfeschlegelsteinhausenbergerdorff, Senior. And that's just an abbreviation -- his actual surname (or so he claimed) was 666 letters long.

    1. Re:They forgot about Wolfe+585 by Princeofcups · · Score: 1

      The article neglects to mention perhaps the most famous case of all, Hubert Blaine Wolfeschlegelsteinhausenbergerdorff, Senior. And that's just an abbreviation -- his actual surname (or so he claimed) was 666 letters long.

      According to wiki, his great-grandfather made up the name. Just another pre-internet troll.

      --
      The only thing worse than a Democrat is a Republican.
    2. Re:They forgot about Wolfe+585 by Anonymous Coward · · Score: 0

      Where the fuck do you think names originally come from if not "made up" by some great-ancestor?

  33. And if you're Irish... by Anonymous Coward · · Score: 0

    My father is of Irish descent, and it's the devil's own job to keep the proper O'(Capital letter) as the start of our last name.

    1. Re: And if you're Irish... by xaxa · · Score: 2

      That's the anglicised version.

      The gaelic original uses Ã".

    2. Re: And if you're Irish... by Anonymous Coward · · Score: 0

      It's amazing perpetual drunks like the Irish could do diacritics to begin with.

    3. Re:And if you're Irish... by Anonymous Coward · · Score: 0

      My father is of Irish descent, and it's the devil's own job to keep the proper O'(Capital letter) as the start of our last name.

      Anonymous O'Coward?
      Anonymous O'coward?

  34. Re:I solved the problem with my long complicated n by Sarten-X · · Score: 3, Insightful

    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.
  35. 0's in phone number by Anonymous Coward · · Score: 0

    I've got a phone number ending in 4 0's. LOTS of sites won't accept it as valid, including my state tax bureau. I had to create an account with a false number, then go back and change it.(and that was at the suggestion of the IT guy from the state!)

    1. Re: 0's in phone number by Anonymous Coward · · Score: 0

      My passport number ends in 123456. Someday I'll be accused of making it up.

  36. osCommerce and its derivatives susceptible to this by stevel · · Score: 2

    I run two e-commerce stores based on osCommerce and had this exact issue with a customer whose last name was Null. There is a common function in osCommerce (tep_not_null) trying to see if the argument is empty. One of the things it looks for is the string "null". When I discovered this, I removed that part of the test (which never made sense to me.)

  37. The real problem by Anonymous Coward · · Score: 0

    As many people have pointed out the obvious, that only an idiot who doesn't know anything about programming would write an app that screws up on a name like "Null", I won't get into that.

    The real problem is the assumptions such as a person have a "first name", a "last name", or a "middle name". Lots of apps mindlessly break things out this way just because they think they are supposed to. It kind of makes sense on some level, especially for form letters, but it breaks a lot. So let's think, what's the ultimate reason for doing that? So that we can use it in natural language: "Mr. Doe", "Dear John", etc.

    But wait... if that's our goal, we are doing it wrong for another reason, gender pronouns. There's the assumption that there is exactly 2, or sometimes the assumption of a 3rd set in the case of marriage. We have this with pronouns, titles, AND names. Are you a Doctor? Do you have a professional Title of some kind? Are you the 10th generation with the same name?

    So what's the solution? Well probably most apps can get away with storing the name in UTF-8 as is, with only a single "name" field. If your app needs to customize or include a name in natural language, perhaps you can auto-conjugate all of the possible forms you'll need and ask the user to edit them for accuracy? That way they can select their own pronouns, etc. Then just store all of the strings verbatim instead of just the string-parts. Probably not the best solution but probably better than most.

  38. Good thing by Anonymous Coward · · Score: 0

    Good thing I named my kid "Drop Database"!

  39. need standards by Tablizer · · Score: 1

    What keeps the Janice Keihanaikukauakahihulihe'ekahaunaele's of the world from not dreaming up even longer last names?

  40. The problem of people named “Null” by khz6955 · · Score: 1

    "Now and again, system administrators have to try and fix the problem for people who are actually named “Null” – but the issue is rare and sometimes surprisingly difficult to solve."

    Not really difficult at all, as “Null” is a text string and NULL is a datatype usually encoded as Ø, that is the numeric value of zero and not "0". Any database that read a string and converts it to a datatype isn't worth the bits it's written in.

    1. Re:The problem of people named “Null” by serviscope_minor · · Score: 1

      Not really difficult in theory.

      In practice if you have a crappy codebase which is full of silly checks on strings as a substitude for proper named parameters, or have a dumbass serialisation stage baked in then it is really difficult. These sort of idiocies can be baked in at deep levels making the fixes very hard.

      --
      SJW n. One who posts facts.
  41. Nani mondai desuka? by Applehu+Akbar · · Score: 1

    The name Mackenzie would be normally rendered in Japanese as three sounds, Ma Ken Ji. Normally these would be phonetic kana characters, and I have never heard of a Jaoanese database (I used to implement these) which didn't support kana. But if you rule out kana names, a foreigner can still choose kanji, or Chinese, characters to represent his name.

    1. Re:Nani mondai desuka? by xlsior · · Score: 1

      The name Mackenzie would be normally rendered in Japanese as three sounds, Ma Ken Ji. Normally these would be phonetic kana characters, and I have never heard of a Jaoanese database (I used to implement these) which didn't support kana. But if you rule out kana names, a foreigner can still choose kanji, or Chinese, characters to represent his name.

      Even then, McKenzie is still a short name, at 8 characters, which happens to break down in chunks that happen to align relatively well into Japanese phonetics -- now try it with a sixteen character Dutch last name, which would take a lot more than three 'sounds' to fit into.

    2. Re:Nani mondai desuka? by Anonymous Coward · · Score: 0

      The name Mackenzie would be normally rendered in Japanese as three sounds, Ma Ken Ji. Normally these would be phonetic kana characters, and I have never heard of a Jaoanese database (I used to implement these) which didn't support kana. But if you rule out kana names, a foreigner can still choose kanji, or Chinese, characters to represent his name.

      These sounds can be used to represent a foreigner, but their legal names are the same as shown on their passport. Government uses that name, so filing taxes (as mentioned in the summary) won't allow you to use the kana spelling. Lets not forget the issue with middle names as well.

      Japan is ass-backward when it comes to dealing with non-japanese names.

  42. HTML filters by HTH+NE1 · · Score: 1

    I tried registering a product on-line, but their software would delete any words found in HTML, including e-mail addresses. My address became something like "user@-word.com" because it had the word "table" in it. Both prompts for it were so filtered. It was also to be my login at the site. I couldn't receive the confirmation e-mail because they'd borked it. I got them on the phone and they made the correction in their database (their system was unfiltered) resulting in me still being locked out because the login prompt also stripped out "table"!

    --
    Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
  43. Holy Haleakala! by Anonymous Coward · · Score: 0

    I mean most of the examples quoted are relatively trivial programming errors or database limitations. All of which need to be fixed forthwith.

    And then we come to Janice Keihanaikukauakahihulihe'ekahaunaele. Holy Haleakala! That's one mighty Hawaiian last name! Can we just call you Janice Keihana informally?

  44. Most websites? Really? by wonkey_monkey · · Score: 1

    When Jennifer Null tries to buy a plane ticket, she gets an error message on most websites.

    Most websites? Really? That's a lot of badly written websites. I mean, wouldn't you have to almost go out of your way to make it crap enough to fall over when giving the string "Null"?

    This is because the word “null” is often inserted into database fields to indicate that there is no data there.

    If you're literally entering the word "null" to indicate no data then you're a really shitty database programmer.

    I can't help wondering if Ms Null had this happen to her once - maybe twice - and enjoyed the attention her little story got her so much that she's started embellishing it each time she tells it.

    --
    systemd is Roko's Basilisk.
    1. Re:Most websites? Really? by dbIII · · Score: 1

      Behind those "lot of badly written websites" (which is possibly also true) could be a single badly written PHP library or even single badly written PHP script that has been cut and pasted from a tutorial site thousands of times.

      It's a guess but there is a lot of crap on websites that the people who put there do not even understand themselves.

  45. Re:I solved the problem with my long complicated n by Drishmung · · Score: 1
    --
    Protoplasm. Quiet Protoplasm. I like quiet protoplasm.
  46. Japan especially terrible by Anonymous Coward · · Score: 0

    1. There are 5 ways to write names which are all used/required depending on situation: Kanji+Kana ; Hiragana ; Full-width Katakana ; Half-width Katakana ; and Roman alphabet. Even Japanese people are fed up with this (cryptic use of half-width katakana is a major cause of bank transfer failures).

    2. A lot of systems make unnecessary strong assumption on names, especially foreigner names: e.g.
    - that there should be no spaces in full name written in full-width characters (OK for Japanese nationals and a handful other countries ; NOK everywhere else)
    - that there should be 1 distinct last name and 1 distinct first name and nothing else (some people have a single word as their only name)
    - that foreigners should have 1 middle name (assuming every foreigners are US citizen and the handful other nationalities which have the concept of "middle" name ; this particular one has led to some of the most infuriating arguments with certain vendors in Japan where it made it impossible for me to register with certain vendors)
    - that there should be 1 first name only (usual practice in some countries is to have multiple first names as distinguishers)
    - restrictions on which characters can be used inside fields (e.g. no hyphens, no space in a given subfield such as last name, typically no support of non ASCII characters)
    - restrictions on field lengths (a classic one everywhere in the world it seems)

    1. Re:Japan especially terrible by hcs_$reboot · · Score: 1

      Not mentioning most sites which design is so f-up that they cannot recognize a number entered while in "hiragana mode" - and force users to switch between modes all te time...

      --
      Slashdot, fix the reply notifications... You won't get away with it...
  47. How is McKenzie too long in Japan? by ayesnymous · · Score: 1

    So a name like Yakamoto would be too long in Japan?

    1. Re:How is McKenzie too long in Japan? by hcs_$reboot · · Score: 1

      No, because "Yamamoto" takes only 2 characters, two ideograms, one for Yama and one for Moto.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    2. Re:How is McKenzie too long in Japan? by Dog-Cow · · Score: 1

      But what about Yakamoto? Which is what the GP actually asked about.

    3. Re:How is McKenzie too long in Japan? by Anonymous Coward · · Score: 0

      Depends on how it is written. If written in either katakana or hiragana (the two most "basic" writing systems) then they would be four symbols long.

      IF the name is written in kanji it can be two or three kanji. Possibly three. I'm not proficient enough to know how it would be written. It cannot possibly be more than four characters long, however.

      McKenzie would be written with the following six katakana symbols MA "TSU" KU KE N JI "I". Because of the fact that the name is foreign there is no way to shorten it using kanji. I would give a more detailed explanation but then I would need the ability to write out the symbols here on slashdot...

    4. Re:How is McKenzie too long in Japan? by suutar · · Score: 1

      From what I've been able to find, it appears that about 92% of japanese family names are 3 characters or less. 99ish% of people have full names (family + given) totalling 6 or less characters, which means 5 or less family name characters. So it's entirely possible that "McKenzie", which I personally would transliterate as "ma-ku-ke-n-ji-i" would be "too long" for a typical form's family name field.

      (main source: http://www.turning-japanese.in...)

    5. Re:How is McKenzie too long in Japan? by suutar · · Score: 1

      Bah. Had a reply to your question, then edited it out and forgot to put it back.

      As far as I can tell, "Yakamoto" is not a family name in use, so it could get transliterated as 2 kanji, 2 kana and 1 kanji, or 4 kana. Depending on the form, that might also be too long, though it seems less likely.

  48. The problem with "Graham-Cumming" by ayesnymous · · Score: 1

    I would have thought the problem would be something else, not the fact that it was hypenated.

  49. Re: I solved the problem with my long complicated by Anonymous Coward · · Score: 0

    I have a friend whose surname is "O" (without quotes). He often is on the verge of a mental breakdown dealing with a web registration form.

  50. Christopher by Anonymous Coward · · Score: 0

    One of the most common first names in the English-speaking world, if not THE most common, doesn't fit on a lot of forms...

  51. Sure, unless they're using Javascript by Anonymous Coward · · Score: 0

    It's pretty easy to imagine that several airlines copied their null test from a crappy stack overflow response using implicit string casting like:

    function isNull(obj) { return obj == "Null" }

    Or maybe that's how the test is coded in some poorly-thought-out JavaScript-on-the-server library that everyone uses.

  52. I suspect a generic SQL injection filter... by WoTG · · Score: 1

    I was stumped working on a website on a shared ColdFusion server, where the webhost decided to install a SQL injection filter. Random form posts and URLs that used various SQL reserved words like, well, LIKE, or SELECT, or whatever started failing. That wasn't fun.

  53. Hyphenated first names by Anonymous Coward · · Score: 0

    ...are sometimes a problem too. And these aren't even that uncommon.

  54. Base Ten by crywalt · · Score: 1

    My New Jersey driver's license still has me named CHRISTOPHE because back in 1993 or so when I got my license -- go ahead, count the number of characters. Ten. The idiot programmers who put together New Jersey's database allocated TEN CHARACTERS for the first name. Fucking morons. First of all, it's standard procedure, when inventing a completely arbitrary length limit in a computer program, to make it a power of 2, just so it looks like you did it for some computer-related reason. A limit of 10 is obviously bullshit because no computer in the world has a limit of 10 for anything. Only humans use 10 as a round number. Second, if you're programming a database of names and you need to set limits on length, the least you should do is check the most common names and make sure the limit is larger than the largest one. And CHRISTOPHER has been in the top twenty of American male first names for a long, long time. Citation: http://www.catb.org/jargon/htm...

    1. Re:Base Ten by david_thornley · · Score: 1

      10-character limits for names smell like COBOL to me. COBOL programmers do not necessarily think like you or me.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    2. Re:Base Ten by crywalt · · Score: 1

      Hey, my wife started out working on COBOL! Okay, actually, she left the job when they started giving her COBOL to do.

  55. Database space is cheap NOW by Bruce66423 · · Score: 1

    The reality is that a lot of systems access databases formatted when that wasn't the case, so are incapable of dealing with larger field sizes because they were set up decades ago. So if the underlying COBOL system won't allow more than 30 characters, it would be foolish to allow a front end that did...

  56. I read once about an Indian guy by tandavanadesan · · Score: 1

    I read once about an Indian guy who changed his name to the equivalent of "John Smith (deceased)". Evidently this was in protest to some threats by a local official along the lines of " if you don't sell me your land you're dead ". The computers were fine with it, but an operator at his bank read the name and flagged the account as deceased, freezing all his money.

  57. Jr by darkain · · Score: 1

    Having a Jr suffix on my name... breaks most web sites. Amtrak being the worst. On one page, it is required, but the on the next page it breaks. Its now impossible with their most recent update for me to purchase tickets using my account. Without the suffix, it says my name doesn't match, but with the suffix, it says there are invalid characters.

    1. Re:Jr by Cederic · · Score: 1

      Serves you right for not changing your name. Stop being subservient to your egotist parent and be your own person.

  58. Re:I solved the problem with my long complicated n by Anonymous Coward · · Score: 0

    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

    An unreasonable expectation. You will inevitably run afoul of the biggest problem all programmers face - other programmers. And then there are banking systems, state laws and other nonsense you have to deal with on regular basis when working in web development.

    catchpa: shackle

  59. Being a Jr sucks just as bad by Anonymous Coward · · Score: 0

    So many web forms ask for First Name, Middle Initial, Last Name. Where the hell is the suffix option????

    Some let me get away with adding " Jr" to the last name, while others bitch fit over the space in the last name. The worst are forms that ask for the name on your credit card by asking "First Name" "Last Name". Uhhh, the name on my card also includes my middle initial and the Jr....

  60. Names that break computers? by l3v1 · · Score: 2

    B.S. It's not names that break computers, it's idiot coders who couldn't care less. I mean seriously, a "Null" as a name to break a name input? Maybe they should write an article about the most idiotic programmers who somehow got to work on real life systems for real money and got away with it.

    --
    I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
    1. Re:Names that break computers? by Tony+Isaac · · Score: 1

      It's not always the programmers. It's often management that allows so ridiculously little time to write and test code, that it only handles the most straightforward cases correctly.

  61. Mediawiki bug by Anonymous Coward · · Score: 0

    Couple of years ago I registered a bug in Mediawiki where the code was sending the string "null" as a null integer. Works perfectly fine in MySQL but presents a type error in Postgresql.

    There is a lot of bad code to be found everywhere.

  62. Names can be hurtful by Anonymous Coward · · Score: 1

    Have 2 high school friends that have terrible problems with names: one pronounces his surname "Azz We Pay," but spells it "Asswipe." Other named Harry Fagina.

  63. Using someone else's computer by tepples · · Score: 1

    The Autocorrect options are very adjustable.

    But how will the adjustments follow the person from one computer to another, even if the person doesn't have a user account on each computer on which he uses Word? Does it support storing a user's roaming settings in a Microsoft account or something? If not, one reason to stick with the defaults and argue for better defaults is to make it easier to use someone else's computer.

    1. Re:Using someone else's computer by thegarbz · · Score: 1

      Good question. I wouldn't know because as a man on the go I typically use my own computer where-ever I am.

      Greetings from an airbnb in Luxembourg :-)

      As for better defaults, Teh is one of the most commonly mistyped first words of an english sentence. Removing it by default because of a minority person's name is quite frankly unbelievably stupid. ... Mind you, so is not providing an easy option to disable autocorrect when you need to.

  64. Last names with spaces by Mike+Van+Pelt · · Score: 1

    I've been dealing with this issue for ... quite a long time, and incompetent programmers have perpetrated code that does some of the weirdest things with my name. Most recently, The Phone Company put my name into Caller-ID as "Pelt Van".

  65. Names that break computers by vandamme · · Score: 1

    My last name is two words. Worse, my cousins have a name which has a punctuation mark (D'Hondt). Either totally screw up a lot of computers.
    Have some pity on Belgians this week, will you? Bedankt.

  66. Any one named Johann Gambolputty ..... here ? by bingoUV · · Score: 1

    Of Ulm?

    --
    Bingo Dictionary - Pragmatist, n. A myopic idealist.
  67. China vs the World by Anonymous Coward · · Score: 0

    I live in China where my generic American name frequently makes it impossible for me to use computer forms. It is common for forms here to not allow anything other than Chinese names, meaning that names with white space or more than five characters are rejected. I remember when I first moved to China I was told at the bank that they could not enter my name into the computer, since their keyboard does not support latin characters (like A or F). After about ten minutes of arguing, I managed to get them to find a way to enter my name. Unicode is not match for ignorance and inappropriate assumptions.

  68. Generational Suffixes: Jr., Sr., II, III, etc. by Anonymous Coward · · Score: 0

    We have to use AMEX Travel at work and they can never get the suffixes over to the Airlines so that it matches the Frequent Flier Account name.

  69. Re:I solved the problem with my long complicated n by painandgreed · · Score: 1

    Ulysses S Grant

  70. lengths allowed by DriveDog · · Score: 1

    It's not just the maxima. I have a one-letter (like x@yyy.zzz) email address that quite a few sites refuse to accept just because it's only one letter long.

  71. Re:I solved the problem with my long complicated n by cthulhu11 · · Score: 1

    A dismaying preponderance of software can't handle an apostrophe in a name, because nobody has ever heard of, eg. Europe. So one sees: o An airline FFM system that accepts it, but a reservation system that doesn't, preventing linkage o Snail mail with ' interpolated into one's name o Web forms that won't submit