"A Thai Airways passenger said he was charged a $94 fee at the airport for a name change because the online booking system would not let him type his full name.
The passenger, whose name was not shared, said when he went to purchase his ticket on the Thai Airways website, his full last name would not fit in the name field. The name field only allows 25 characters for surname. The passenger tried shortening his name on the website and was finally able to buy tickets for himself and his family, the Bangkok Post reported."
Traveler charged extra booking fee for having a long last name
I think that computers have complicated lives very greatly.
(Score: 5, Insightful) by edIII on Saturday May 12 2018, @07:50AM (6 children)
Ohh, fuck you. That's just a bigoted response. There are plenty of cultures in the world that have very long names, at least when spelled. There is nothing monstrous about that.
What it demonstrates is that the programmers don't give a fuck about names they don't commonly deal with. If you took a list of English names, grabbed the longest one, yeah, it's going to sure as fuck shorter than most Thai names.
Also, It's fucking 2018. We're not starved for data capacity, and you can easily grant 256 characters of space (varchar(255)). Limiting names to 20 characters makes no fucking sense, not at least from a database perspective.
Which means you're just an ignorant bigot who doesn't want to deal with the unknown, like a culture that would come up with a 30+ character last name.
Technically, lunchtime is at any moment. It's just a wave function.
(Score: 0) by Anonymous Coward on Saturday May 12 2018, @07:54AM (1 child)
VarChar an indeded field? You must be a VB ... coder..
(Score: 0) by Anonymous Coward on Sunday May 13 2018, @02:07PM
in 2018 it changes almost nothing do some benchmarks before blabbering nonsense, choosing the right index collation does for query speed than switching a varchar(255) to a char(255).
(Score: 1, Troll) by unauthorized on Saturday May 12 2018, @10:56AM (2 children)
It's monstrous to saddle the kid with such an annoying-to-use name.
And they shouldn't. Just because some hipster decides to name their kids with a unique combination of smells, programmers across the world are in no way obliged to add olfactic input fields to every form they create.
(Score: 3, Insightful) by requerdanos on Saturday May 12 2018, @01:43PM (1 child)
Perhaps, but the kid's name is likely normal-sounding and completely non-annoying.
The intersection of the culture in which that's true, and the up-and-coming global information systems culture, means that a pretty normal, unexceptional (if uncommon) name gives IT a challenge in the case of short-to-medium length data fields.
Making it worse was their reaction. "We suck, so that's going to cost you $94."
(Score: 2) by unauthorized on Saturday May 12 2018, @11:31PM
Until it comes time to write it down.
(Score: 2) by acid andy on Saturday May 12 2018, @12:06PM
You're right. February 29th birthdays are another example of lazy coders not giving a crap about the edge cases. Two digit years as well. There must be centenarians out there unable to pay their bills.
If a cat has kittens, does a rat have rittens, a bat bittens and a mat mittens?