Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

CASTing Expand / Collapse
Author
Message
Posted Friday, May 30, 2008 5:42 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, May 26, 2011 11:54 AM
Points: 74, Visits: 8
Thanks for the clarification. :D
Post #508975
Posted Friday, May 30, 2008 10:55 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, June 01, 2009 11:17 AM
Points: 371, Visits: 44
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

Best Regards,
Chris Büttner



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?
Post #509260
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse