Hugo Kornelis (4/15/2013)
Calling a column ID and then putting duplicate values in it is just evil. No raise for the developer who wrote this, and a warning that (s)he'll be fired if it happens again.And not noticing it while working out the result of a QotD in my head is just stupid *facepalm*. No raise for me either.
Nor for me. I feel quite an idiot for falling for it. :blush:
I do not really like what currently appears to be in fashion here, to write what appears to be a question about a SQL feature, but that actually tests our ability to detect sneaky issues that are hidden in the question and/or code. Yes, I know that being made responsible for existing code often is the same. I don't mind such questions every now and then. But I have this feeling (not based on any actual counting) that there are a bit too many of them lately.
Trick questions are a part of life. If there are too many we could try shooting the people who write them if both (a) we have any bullets left after we finish the politicians, bankers, economists, and lawyers and (b) we manage to stay out of gaol after dealing with the P,B, E and L. :hehe:
Tom