[
https://issues.apache.org/jira/browse/JENA-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493296#comment-17493296
]
Andy Seaborne commented on JENA-2282:
-------------------------------------
Yes - except I suggest a completely separate dataset and sparql endpoint, not
just a separate graph inside the data being worked on. Then the data never gets
mixed with the query workbench.
A common pattern is to have "default union graph" - that would see the queries
stored (and count their triples with {{COUNT}}).
Config files are in-memory graph from from file but they are more transitory at
runtime.
Since we have mechanism (= "hammer"!) in persistent datasets, tackling the
problem that way reuses the transactional persistence. It does to even have to
be in the same server as the data - think of it as a assistant for working on
any remote data, not Fuseki specific for the data of interest.
> Fuseki2 Query Store
> -------------------
>
> Key: JENA-2282
> URL: https://issues.apache.org/jira/browse/JENA-2282
> Project: Apache Jena
> Issue Type: Wish
> Components: Fuseki UI
> Affects Versions: Jena 4.4.0
> Reporter: Nicholas
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Many triplestore applications have a way to store SPARQL queries. These sorts
> of application parts are really useful: you can keep coming back to useful
> queries. If the queries can be named, then you can build up a query library.
> Not hard to make and super useful. Unless there is already an extension for
> this or plans for such, I'm happy to (have my staff) give this a go!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
