Ah, we call him little bobby tables. http://xkcd.com/327/
We have an employee whose last name is Null. He kills our employee lookup (2012)
31–40 of 245 posts
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#32Why would null be confused with "null"? It shouldn't be a problem.
(a) standards
(b) poorly implemented standards
(c) poorly implemented programmers :-)
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#33Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#34COALESCE(LASTNAME, ''), how hard is that?
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#35Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#36Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#37Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#38Reminds me of a story a police reservist told me. Guy got a license plate caled "none," and instantly had thousands of outstanding warrants. (The cop thought "none" was trying a fast one, and so deserved it.)
The article is pretty entertaining - it talks about him becoming semi-famous and getting pulled over because cops wanted their picture taken with him: http://articles.latimes.com/1986-06-23/news/vw-20054_1_licen...
The comp.risks article (where I originally read about this) is also amusing: http://catless.ncl.ac.uk/Risks/6.45.html
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#39I had an aunt named Nan, I wonder what her disbursement checks were like :-)
I have a friend named Nan, and I posted every "NaN" error I got in my code on her Facebook wall for about a year. She hated it.