Excluding "starts with underscore" filters out all objects
I can find no guidance on filter patterns. We have a lot of "temporary" tables which start with an underscore. We've previously used object filters to exclude anything which starts with an underscore. This now excludes all objects in the database, presumably because it's using SQL wildcards. Is the filter syntax SSC uses specified anywhere?
Tim Golden
shared this idea
As of SQL Source Control 3.8.13, filter rules now support the standard T-SQL LIKE syntax for wildcard characters (‘%’, ‘_’, ‘[abc]’, and ‘[^abc]’ – see MSDN for details).
To include wildcard characters explicitly in a filter, they can be escaped with square brackets.
‘Equals’ and ‘Does not equal’ operators will not treat those characters as special wildcard characters.
-
mark
commented
Please show this some love as it causes a manual checkbox process every time, I compare and sync.
-
Jonny Johansson
commented
This is something that would take 5 minutes for RedGate to fix, just escape all characters that are SQL wildcards. As I see it, this is a bug, and it's astounding that it hasn't been fixed for several years!
-
Nik
commented
Agree with others.... we also have patern for temporary tables in development like _tableName which must be excluded from comparision. We have tried with escape but no luck. Please add escape sequence.
-
Ryan
commented
I agree. this feature would be very helpful!
-
Jonathan Jones
commented
I agree - please add an escape sequence. This is not a good bug being that the underscore is always treated as a wildcard. objects such as test_table and testing become equivalent in the comparison if your compare expression is test_
-
Eugene Furer
commented
Agree with last comment. Please add escape sequence for all special characters
-
Jason
commented
Please include this feature. Or better, an escape sequence so we don't have to worry about other characters in the future like percent signs.