Skip to content
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

Query without 'PREFIX' is endlessly waiting for a response #298

Closed
graue70 opened this issue Dec 25, 2019 · 3 comments
Closed

Query without 'PREFIX' is endlessly waiting for a response #298

graue70 opened this issue Dec 25, 2019 · 3 comments

Comments

@graue70
Copy link
Contributor

graue70 commented Dec 25, 2019

The following query gives the correct result fast:

PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
SELECT ?o2 WHERE {
  wd:Q80728 ?p1 ?o1 .
  ?o1 wdt:P1477 ?o2 .
}

The following (semantically identical) query never finishes. It keeps 'Waiting for response':

SELECT ?o2 where {
  <http://www.wikidata.org/entity/Q80728> ?p1 ?o1 .
  ?o1 <http://www.wikidata.org/prop/direct/P1477> ?o2 .
}

The two entities are recognized correctly when hovering over them. (The same query works on wdqs.)
The console gives the following error message:

TypeError: /SELECT(?: DISTINCT)?([^]*)WHERE/.exec(...) is null qleverUI.js:257:63
    processQuery http://qlever.informatik.uni-freiburg.de/static/js/qleverUI.js:257
@hannahbast
Copy link
Member

@hannahbast
Copy link
Member

It also works in the QLever UI if you capitalize the WHERE:

SELECT ?o2 WHERE {
  <http://www.wikidata.org/entity/Q80728> ?p1 ?o1 .
  ?o1 <http://www.wikidata.org/prop/direct/P1477> ?o2 .
}

@hannahbast
Copy link
Member

I have created an issue in the QLever UI project over here: ad-freiburg/qlever-ui#3

I am closing this issue because there is nothing wrong with the QLever backend with respect to this bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants