Hi @pmualaba - this is certainly useful functionality, however wrapping in a toLower() call would mean that an index could not be used for the comparison, which would significantly impact performance for larger datasets. Ideally we can expose this functionality through a fulltext index, which would ensure performant filtering for case insensitive comparisons. We had some thoughts on this in #266

You can accomplish this functionality now by creating a Query field using a @cypher directive.

type Query {
  productContains(searchString: String): [Product] @cypher(statement: """
    MATCH (p:Product)
    WHERE toLower(p.name) CONTAINS toLower($searchString)
    RETURN p
  """
}

See also #261

Hi @johnymontana, we are also having some issues regarding case sensitive search using the _contains filter. The schema we're using is rather large and we are developing a flexible search interface which should be able to search on almost any field.

Would there be any downside by adding a new filter type which uses the regex operator?

For example:

query {
  MusicComposition (filter: { OR: [{ name_like: "(?i)el rossinyol.*" }], [{ creator_like: "(?i)el rossinyol.*" }] })  {
    identifier
    name
    creator
  }
}

Which resolves to the following cypher query:

MATCH (musicComposition:MusicComposition) 
WHERE (musicComposition.name =~ "(?i)el rossinyol.*") OR (musicComposition.creator =~"(?i)el rossinyol.*")
RETURN musicComposition { .identifier , .name, .creator } AS musicComposition

Perhaps like is not the best keyword to prevent confusion/behaviour difference with the SQL like operator.

#608