You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an issue when try to use "?" not as a parameter in the 'Like' statement, but as part of word. For example "message like '%blabla?%". Currently I got an exception because 'Sqlkata' uses question mark as a parameter placeholder. So I need a way to escape question mark. Or, actually, when I opened the source code of 'Complier.cs' I found something interesting. Here we have: protected virtual string parameterPlaceholder { get; set; } = "?";
It is good opportunity to override it and use some other symbol or even word for the binding parameter, but, for some reason this property isn't used elsewhere. For example:
So could you please reuse 'parameterPlaceholder' parameter in all other places so that it can only be changed in one place, without having to override all of these methods? Or add possibility to escape it in queries
The text was updated successfully, but these errors were encountered:
I have an issue when try to use "?" not as a parameter in the 'Like' statement, but as part of word. For example "message like '%blabla?%". Currently I got an exception because 'Sqlkata' uses question mark as a parameter placeholder. So I need a way to escape question mark. Or, actually, when I opened the source code of 'Complier.cs' I found something interesting. Here we have:
protected virtual string parameterPlaceholder { get; set; } = "?";
It is good opportunity to override it and use some other symbol or even word for the binding parameter, but, for some reason this property isn't used elsewhere. For example:
ctx.RawSql = Helper.ExpandParameters(ctx.RawSql, "?", ctx.Bindings.ToArray());
So could you please reuse 'parameterPlaceholder' parameter in all other places so that it can only be changed in one place, without having to override all of these methods? Or add possibility to escape it in queries
The text was updated successfully, but these errors were encountered: