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
When making a request with a filter that uses the ``like`` operator, the
user will likely provide an argument of the form ``%somestring%``. If
not properly URL encoded, this will be interpreted on the server side as
an unintended string.
This fixes#331 and #415.
Ah, encoding it works! Was pasting the queries into the address bar, I thought the browser would do the encoding automatically. Odd that "Something%" does work without explicitly encoding.
Consider the following SQL query, it gives me back one database row:
I would expect the following query to produce the same, but I get zero results:
When I search for "Something%", I do get back the same row as the SQL query.
The text was updated successfully, but these errors were encountered: