You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to support case-insensitive field comparisons especially in addition to CONTAINS.
This could translate to two TOLOWER() calls for now. This might be another operator CONTAINS_INSENSITIVE or it might be an option to change the case sensitivity per query.
I know that the same can be achieved by using a regular expression, but it's difficult for the client and does not using indexes.
Obviously the TOLOWER() does also not use indexes, but this seems like an issue that could still be addressed in neo4j and at least the client could send reasonable queries.
The text was updated successfully, but these errors were encountered:
It would be nice to support case-insensitive field comparisons especially in addition to CONTAINS.
This could translate to two TOLOWER() calls for now. This might be another operator CONTAINS_INSENSITIVE or it might be an option to change the case sensitivity per query.
I know that the same can be achieved by using a regular expression, but it's difficult for the client and does not using indexes.
Obviously the TOLOWER() does also not use indexes, but this seems like an issue that could still be addressed in neo4j and at least the client could send reasonable queries.
The text was updated successfully, but these errors were encountered: