It *can* be done right now, but it should be much easier to drop in custom query clauses.

Marking Design Decision Needed because I'm not *fundamentally* opposed to the idea however, unless someone from the core is particularly enamoured with the idea, I think it's a wontfix.Īs an aside, I *would* be in favour of anything that would make it easier for you to add this filter clause as a third party extension. Personally, I'm not inclined to add a feature duplicating existing functionality just to work around deficiencies in MySQL's indexing mechanisms. This is not in the SQL standard but is a. There is evidently a big difference under MySQL, but the same apparently can't be said about Postgres. The key word ILIKE can be used instead of LIKE to make the match case-insensitive according to the active locale. I'd also need to see evidence that a LIKE query is faster than the analogous regex-based query, for all databases. In another word, we can say that like is a pattern matching operator. By using the like functionality or clause, we can match the specified pattern as per our requirement. In addition, Django's ORM tries to be avoid exposing SQL-specific features as much as possible, and LIKE syntax is about as SQL specific as you can get. PL/SQL provides the different types of functionality to the user, basically like is one type of functionality that the PL/SQL provides. In contrast, LIKE syntax has limited capabilities, and is available only in SQL. Regular expressions are a more powerful search syntax, and they are a syntax that is familiar in many other contexts. I'm not sure I agree that LIKE syntax is more readable. On the whole, I'm not convinced that this proposal is beneficial.

Like ilike sql