-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SqlKata generating query with unfulfilled parameters #62
Comments
I just saw, that the RawSql parameter contains
though I'm still confused as to why, since I'm passing the dictionary, expecting the wildcards to be replaced with the actual values I set. |
This what is called parameters bindings, which is recommended to execute queries, for debugging purposes you can use the Check https://stackoverflow.com/a/4712113/1104402 for more info |
Well, I know parameterized queries, though I'm confused as to why the values aren't included in the query by the get-go. Maybe as a feature request, you could have a parameter, which has the values in the query right away, properly escaped (maybe like SqlFull), so you aren't forced to use parameterized queries. |
thanks for your suggestion, but including the values directly in the generated sql open the door for unsecure/un-efficient code, this is why I am against this approach |
I have the following
Dictionary<string, object>
called datensaetze:Compiling this into a query:
results in the following query:
which is not executable. I can't use the QueryFactory, because I need the SQL string logged in a log file and possibly edited (see #60 )
The text was updated successfully, but these errors were encountered: