Like statement is not case-sensitive in SQLite backend

[Ali]

Like statement is not case-sensitive in SQLite backend.
I know that was mentioned in the documentation, but I think the Glob statement may solve it or the alternative statements for Like,
the contains and icontains lookup has the same behavior because using the Like statement in the query, like this :

 "SELECT ### FROM #### WHERE ### LIKE %####%"

but we can change it to this :

"SELECT ### FROM #### WHERE ### GLOB *####*"

for contains lookup in the SQLite backend, because the Glob statement is case-sensitive,the Regex statement also its a candidate

[Mariusz Felisiak]

Duplicate of #15659, see comment:

"but looking at GLOB, this doesn't seem possible, because it cannot be used as a drop in replacement for LIKE with different wildcards, since it lacks the ESCAPE clause that LIKE has, which we need"

[Ali]

Replying to Mariusz Felisiak:

Duplicate of #15659, see comment:

"but looking at GLOB, this doesn't seem possible, because it cannot be used as a drop in replacement for LIKE with different wildcards, since it lacks the ESCAPE clause that LIKE has, which we need"

We have PRAGMA statement called case_sensitive_like, which is designed to specifically make the LIKE operator case-sensitive for ASCII characters, see the ​document, so we can use it to fix this?

[Mariusz Felisiak]

Replying to Ali:

We have PRAGMA statement called case_sensitive_like, which is designed to specifically make the LIKE operator case-sensitive for ASCII characters, see the ​document, so we can use it to fix this?

This is also discussed in the original ticket:

" (With the case_sensitive_like=true, just the top left is changed, which is not an improvement). Unfortunately, this means we've got problems with Unicode whichever way we go, because we don't have a way of doing case insensitive matching. "