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

Named Subqueries #43

Open
JonasKress opened this issue Aug 10, 2017 · 7 comments
Open

Named Subqueries #43

JonasKress opened this issue Aug 10, 2017 · 7 comments

Comments

@JonasKress
Copy link

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

@RubenVerborgh
Copy link
Owner

Thanks for the suggestion. Are these used often? I haven't encountered them myself.

@fnielsen
Copy link

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

@lucaswerkmeister
Copy link
Contributor

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).

@RubenVerborgh
Copy link
Owner

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.

@JonasKress
Copy link
Author

JonasKress commented Aug 11, 2017

This is very important for us and I have seen that there are other non standard features already part of this library.

@RubenVerborgh
Copy link
Owner

The issue you linked to is about the non-standard feature DEFINE, which is not part of this library.

@RubenVerborgh
Copy link
Owner

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.

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

No branches or pull requests

4 participants