-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is REGEX case insensitive now? #1314
Comments
@belett The REGEX function itself is case-insensitive if and only if the "i" flag is provided. For example https://qlever.cs.uni-freiburg.de/wikidata/huiLRw (astronauts with name matching "neil", zero results) and https://qlever.cs.uni-freiburg.de/wikidata/U7OafN (astronauts with name matching "Neil", two results). However, QLever has an optimized implementation for prefix search, that is, a REGEX starting with a Does this answer your question? |
Thanks, it does answer most of my question. Indeed, I was looking for prefix (with query like https://qlever.cs.uni-freiburg.de/wikidata/AT4L5i where I look for French labels starting with "Église" instead of "église"). Do you have an idea when it will be fixed? And is there a way around until then? |
@belett Yes, there is an easy workaround. As I said, the optimization is only triggered for REGEXes for the form |
Hi,
It seems to me that REGEX was case sensitive (as in the SPARQL standard) and is now case insensitive.
Is my impression right?
And if so, s a workaround, how can I can make it case sensitive again? (I know that REGEX has a flag "i" to make it case insensitive but I can't find a flag to make it case sensitive - as it's the default)
Cheers, Nicolas
The text was updated successfully, but these errors were encountered: