🐛 FIX: SQLite: apply escape \
in QueryBuilder like
and ilike
#5553
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For
like
andilike
, the special characters_
and%
may need to be escaped if they have literal meanings (LIKE .. ESCAPE
in SQL) . However, the sqlite backends do not implicity treat\
as escape sequence (unlike Postgres). https://sqlite.org/lang_expr.htmlI discovered this bug when using the SQLite backend (in memory) with
aiida-vasp
where one of the entry point has name with an underscore. Querying such node gets escaped like:Here the
_
is automatically escaped, but the query only works fine with the psql backend, with sqlite it does not match any existing objects.This PR makes
\
to pass explicity as escaping character for sqlite backends. The use of\
for escapign is already hard-coded aiida.Here is an example test script: