Deal with in clauses in SQL Server


#**************************************************************************
#********** Aspire string substitution support
#**************************************************************************
aspire.substitutions.quote=aspire.translators.OracleQuote
aspire.substitutions.empty=aspire.translators.GeneralTranslator
aspire.substitutions.urlEncode=aspire.translators.GeneralTranslator

# future stuff
request.aspire.translators.quote.className=com.ai.common.SimpleQuoteTranslator
request.aspire.translators.OracleQuote.className=com.ai.common.OracleQuoteTranslator
request.aspire.translators.GeneralTranslator.className=com.ai.common.GeneralTranslator

#06/25/2012: Supports in clauses based on ids
aspire.substitutions.sqlids=aspire.translators.sqlids1
aspire.substitutions.sqlstrings=aspire.translators.sqlstrings

request.aspire.translators.sqlids.className=com.ai.common.SQLInIdsClauseTranslator
request.aspire.translators.sqlids1.className=com.ai.common.SQLServerInIdsClauseTranslator
request.aspire.translators.sqlstrings.className=com.ai.common.SQLInStringsClauseTranslator

in ({some-ids.sqlids})

or

in ({some-strings.sqlstrings})

in (null)

in response to "arg1,arg2,arg3"
in ('arg1','arg2','arg3')

if empty

in ('')

Of course you can do this in the stored proc if you want to