-
Notifications
You must be signed in to change notification settings - Fork 66
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
Named Subqueries #43
Comments
Thanks for the suggestion. Are these used often? I haven't encountered them myself. |
We are using WITH quite often in Scholia: If the labeling SERVICE is included in the first SELECT we get a slow performance. It is possible that multiple selects perform just as well. There are a few on this page, for instance: https://tools.wmflabs.org/scholia/organization/Q1137665 |
Yes, in general, named subqueries are a more reliable optimization than regular subqueries (BlazeGraph executes the named subqueries only once, before the rest of the query, whereas it sometimes seems to do strange things for regular subqueries). |
Thanks for the info. I'm reluctant to implement a non-standard feature, but I'll leave this issue open so it can be taken into consideration. |
This is very important for us and I have seen that there are other non standard features already part of this library. |
The issue you linked to is about the non-standard feature |
That said, I'm willing to consider a pull request for named subqueries, on the condition that it is configurable and switched off by default. |
It would be nice if Named Subqueries would be supported, even though they are not part of the SPARQL spec:
https://wiki.blazegraph.com/wiki/index.php/NamedSubquery
The text was updated successfully, but these errors were encountered: