| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Same problem here :) I have a json column containing an object with question mark field like this:
if I create a sqlkata WhereRaw query like :
I get the stack:
@ahmad-moussawi , can you take a look at it ? |
Sorry, something went wrong.
|
@toburger I see that there is still some reference of the ? still hardcoded, in the Firebird and SQLiteCompiler, |
Sorry, something went wrong.
|
Sorry, don't know what happened. It has closed the PR automatically. |
Sorry, something went wrong.
… is hardcoded to a ? Added compiler to the constructor of SqlResult Made ParameterPlaceholder public
|
Hi, just created the PR #628 for the SqlResult class still containing the question mark hardcoded |
Sorry, something went wrong.
… is hardcoded to a ? Added compiler to the constructor of SqlResult Made ParameterPlaceholder public
… is hardcoded to a ?
| Back | FazBrowse Home | New Git URL |
There are places where the parameterPlaceholder variable isn't used and the ? (question mark) is hardcoded in code.
This prevents the redefinition of the parameterPlaceholder to another value.
Practical usage:
It is not possible to define JSON (Postgres) specific queries because some of the keywords use the question mark.
Example:
The ? gets interpreted as a parameter and throws an exception.
With the changes in place the parameterPlaceholder can be redefined to use another value, for example the $$ value can be used insetad by inheriting a new class from e.g. PostgresCompiler:
Now the query works as expected after all desired occurrences of ? are replaced with $$ in your code.