Re:An employee, whose last name is Null, kills our employee ...
by joejohnson on Friday April 27, 2012 @02:16PM
(#3900355)
I think this is a joke, possibly inspired by the XKCD comic (link posted in the stackoverflow comments). The string "Null" would not cause this behavior.
[ Parent
| on HN ]
Re:An employee, whose last name is Null, kills our employee ...
by pohl on Friday April 27, 2012 @02:38PM
(#3900498)
I have personally encountered "Null" as a surname in system used by job applicants world-wide. The system's session layer encodes absent values as the string "null" at some point. The Null clan is the only problematic case, and they are numerous enough that the maintainers are aware of the problem but not so numerous to fix the session layer.
I wish I could listen in on a dinner conversation at Null house. They must have an interesting perspective about computers.
Re:An employee, whose last name is Null, kills our employee ...
by tlrobinson on Friday April 27, 2012 @02:26PM
(#3900412)
'The string "Null" should not cause this behavior.'
FTFY. It's certainly possible there's a bug in the library.
Re:An employee, whose last name is Null, kills our employee ...
by Yarnage on Friday April 27, 2012 @02:28PM
(#3900427)
The OP claims it's real. After dealing with some SOAP systems I would entirely believe this is possible.
Re:An employee, whose last name is Null, kills our employee ...
by unfletch on Friday April 27, 2012 @07:28PM
(#3901493)
I know someone named Null who's had similar problems as a user of web apps. In fact I mentioned it here a while back: http://news.ycombinator.com/item?id=1440890
Re:An employee, whose last name is Null, kills our employee ...
by Bobby_Tables on Friday April 27, 2012 @04:50PM
(#3900987)
It could very easily be real. I was in a Fantasy Football league on Yahoo a few years ago, and there was a player named Keith Null who played briefly after another player was injured. His name just showed up as Keith.