--
Ticket URL: <https://code.djangoproject.com/ticket/33849>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => duplicate
Comment:
Duplicate of #15659, see
[https://code.djangoproject.com/ticket/15659#comment:8 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"''
--
Ticket URL: <https://code.djangoproject.com/ticket/33849#comment:1>
Comment (by Ali):
Replying to [comment:1 Mariusz Felisiak]:
> Duplicate of #15659, see
[https://code.djangoproject.com/ticket/15659#comment:8 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
[https://www.sqlite.org/pragma.html#pragma_case_sensitive_like document],
so we can use it to fix this?
--
Ticket URL: <https://code.djangoproject.com/ticket/33849#comment:2>
Comment (by Mariusz Felisiak):
Replying to [comment:2 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
[https://www.sqlite.org/pragma.html#pragma_case_sensitive_like 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. "''
--
Ticket URL: <https://code.djangoproject.com/ticket/33849#comment:3>