Skip to content

[tuning.xml#range]: misleading wording concerning regular expressions #1070

Open
@daliboris

Description

@daliboris

Regular expressions don't support ^ metacharacter

For queries on string content, range indexes work well for exact comparisons (author = 'Joe Doe') or regular expressions (matches(author, "^Joe.*")) You can also use a full text index for the latter.

  • The above formulation suggests that eXist-db allows the use of the ^ metacharacter to match the starting position within the string in a regular expression. eXist-db uses Lucene 4.10.4 for full text search and according to the documentation, this metacharacter is not allowed.

  • missing fullstop after ))

Proposed wording

For queries on string content, range indexes work well for exact comparisons (author = 'Joe Doe') or regular expressions (matches(author, "Joe.*")). You can also use a full text index for the latter, but be aware that not all metacharacters and patterns of regular expressions are allowed, for instance caret (^) to match the starting position. See the Lucene documentation for more details.

Please provide the following

  • exist-db version: 6.2.0
  • documentation version: 6.2.0

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions