think these two QODs really show how evil implicit type conversions are.
Id rather spend this one second on explicit type conversion than on reviewing such code for possible data loss caused by implicit conversion.
I had to look at this QOD for at least 5 seconds before I made my choice. Sum this up for all your code and then tell me: wouldn't it be great if the compiler told you when you had missed a type conversion?
Sure, you have a test team, but why not catch an error in the first place?
Isn't a database a realm where datatypes should be handled in the most strict way?
Just some thoughts in the late evening :-)
I totally agree after thinking about these two QOD (great ones, btw). Is there a way to enable explicit (strict) conversions when writing stored procedures in SQL 2005?