RE: [Dunit-interest] Is Dynamic SQL worth refactoring?

[Morris, C. <chr...@sn...>]

I'd say yes. Your code change looks good to me. 

I have an app that is responsible for selecting a bunch of data from a bunch
of different tables to do an intelligent sync with a master database. It's a
real pain because the schemas are quite different. 

But I have a lot of common SQL statements that require similar, complex
criteria. I took what was common about them, made it a 'template' so to
speak, pass variables to a set of routines that construct the SQL statement
me for me. To have separate hard-coded SQL statements would be a high amount
of duplication and a breeding ground for bugs.

Chris