The smellsLikeOleDb regex on SqlMapper doesn't work correctly in all kinds of scenarios. If you are passing a model that has properties that you don't intend to parameterize and cannot be parameterized this results in a NotSupportedException
I think this would most easily solved by having a setting turn it off on this line (just make filterParams true and ignore this regex if a setting is enabled)
| filterParams=!smellsLikeOleDb.IsMatch(identity.sql); |
Some examples that break this "smell check".
This would all be solved by having a way to turn it off (make filterParams true and ignore this regex)
I see no reason not to have the option to disable this footgun completely for anyone not using OLEDB at all. For that matter... why not default it to off and let anyone using OLEDB turn it on?
The smellsLikeOleDb regex on SqlMapper doesn't work correctly in all kinds of scenarios. If you are passing a model that has properties that you don't intend to parameterize and cannot be parameterized this results in a NotSupportedException
I think this would most easily solved by having a setting turn it off on this line (just make filterParams true and ignore this regex if a setting is enabled)
Dapper/Dapper/SqlMapper.cs
Line 2538 in 47ef1e7
Some examples that break this "smell check".
Question marks in SQL Comments
-- Why is the question mark in this comment treated as a parameter ?Question marks in strings. Issue with handling '?' character in SQL strings when using SQL Server #1914
Using openquery execute LDAP Queries that start with
<LDAP://:>;Postgres type casts Postgres type cast is interpreted as parameter #1299
This would all be solved by having a way to turn it off (make filterParams true and ignore this regex)
I see no reason not to have the option to disable this footgun completely for anyone not using OLEDB at all. For that matter... why not default it to off and let anyone using OLEDB turn it on?