Setup sparqly service at https://sparqly.wmflabs.org/ (like Quarry)
Open, LowPublic

Description

Quarry (https://quarry.wmflabs.org/) is a web service where people can make SQL queries and share these queries and the result. It's a really nice service to get to know SQL.

Since a couple of months we have the Wikidata Query Service (http://wdqs-beta.wmflabs.org/) which uses SPARQL. Not a lot of people know a lot of sparql so having some sort of service like Quarry, but for SPARQL , would make it a lot easier to use this service.

Proposed name is sparqly, but we can always bike shed over a better name.

Multichill updated the task description. (Show Details)
Multichill raised the priority of this task from to Needs Triage.
Multichill added subscribers: Multichill, Nikki.
Restricted Application added projects: Wikidata, Discovery. · View Herald TranscriptJul 4 2015, 8:26 AM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

I think it'll be simpler to just have Quarry handle SPARQL as well.

I think it'll be simpler to just have Quarry handle SPARQL as well.

Fine with me too :-)

Addshore added a subscriber: Addshore.
Lydia_Pintscher moved this task from incoming to hold on the Wikidata board.Jul 4 2015, 8:42 PM
Smalyshev moved this task from Needs triage to WDQS on the Discovery board.Jul 7 2015, 8:55 PM
Capt_Swing set Security to None.
Sitic added a subscriber: Sitic.Jul 17 2015, 8:37 PM
Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptJan 14 2016, 7:44 AM
Base added a subscriber: Base.May 6 2016, 1:44 PM

A stupid question by a person with bad SQL (progressed from almost zero mostly thanks to quarry) and almost no SPARQL knowledge: would it be possible to have part of a request being made in SQL and part in SPARQL and have it all output as one table? (Like select a list of articles on some wiki by some WD based criteria and then fetch its sizes, creators and stuff like this via SQL and just have it all in one table)

A stupid question by a person with bad SQL (progressed from almost zero mostly thanks to quarry) and almost no SPARQL knowledge: would it be possible to have part of a request being made in SQL and part in SPARQL and have it all output as one table? (Like select a list of articles on some wiki by some WD based criteria and then fetch its sizes, creators and stuff like this via SQL and just have it all in one table)

Quite off topic on this bug. Another forum like the wikidata mailinglist is probably more suitable. Have a look at https://petscan.wmflabs.org/ . With that tool you can combine queries from different sources.

Base added a comment.May 6 2016, 3:45 PM

A stupid question by a person with bad SQL (progressed from almost zero mostly thanks to quarry) and almost no SPARQL knowledge: would it be possible to have part of a request being made in SQL and part in SPARQL and have it all output as one table? (Like select a list of articles on some wiki by some WD based criteria and then fetch its sizes, creators and stuff like this via SQL and just have it all in one table)

Quite off topic on this bug. Another forum like the wikidata mailinglist is probably more suitable. Have a look at https://petscan.wmflabs.org/ . With that tool you can combine queries from different sources.

More simply I guess that means the answer is no. Thanks, that's what I wanted to hear :)

Smalyshev triaged this task as Low priority.Sep 12 2016, 10:37 PM

With the current SPARQL setup it's easy to share queries either by full url or by short url. I think we can close this one.

Base added a comment.Sep 14 2016, 10:49 AM

Do I get it right that now a query cannot be longer than URL length limit? How much exactly is that number? I wonder if there were cases of people needing to run longer queries. Is this investigable somehow?

@Base, your questions are very interesting, and you seem to have really nice suggestions, but I would suggest a mailing list, wiki talk page (or if it was a bug/feature request, doing them on a separate ticket), as the preferred way to communicate.

This ticket is probably going to be closed soon, and when that happens your questions will get unanswered and with little visibility here.