November 19, 2015 at 4:18 pm
Lynn Pettis (11/19/2015)
If the source data is supposed to integer data and it isn't, then I actually agree with the developers and the need to hunt down and fix the bad data. If you use a strongly type method and you still have bad data that can't be converted to an integer, then you haven't solved the problem.
Source is column defined as sql_variant, so the data can be any base type ;-). The conversion error occurs about 15-20 statements after its FOR XML PATH munging into a delimited list of "integers". No checking of sql_variant's base types was done before munging, and that is clearly a poor coding practice.
None of this is under my control (if it were, it wouldn't have happened). Developer A defined the sql_variant data type. Developer B created the delimited list (without checking base type). Developer C parsed the passed delimited list as integers. Developer C insists on handling integers. Developer D wants to fix the sql_variant's value. Developer B is taking it easy:smooooth:, instead of fixing the problem :ermm:).
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply