[deleted]
We have an employee whose last name is Null. He kills our employee lookup (2012)
11–20 of 245 posts
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#12If my last name were Null, I'd totally call my son Dave!
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#13Not even reading the article. Just upvoting for the title alone.
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#14Reminds 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.)
If it's the same one I remember the plate was "NO TAGS"[1].
[1]: http://www.huffingtonpost.com/2012/02/16/no-tags-meet-sauced...
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#15If my last name were Null, I'd totally call my son Dave!
Or Devon. Dev for short.
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#16COALESCE(LASTNAME, ''), how hard is that?
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#17Vaguely related but we had a customer using some feature that split text blobs using a record separator. One time someone wanted to not split at all and set separator="none" without bothering to look up how to actually turn off record splitting. It worked well enough in quick tests, but by the time we'd gotten the support call, they'd corrupted a massive database where every product with a description containing the string "none" was now corrupted.
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#18Ah, we call him little bobby tables. http://xkcd.com/327/
damn, i was so late!
Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#19Re: We have an employee whose last name is Null. He kills our employee lookup (2012)
#20Are his initial M. T.?