oxigraph-query(1)
๐ oxigraph-query โ bestie edition ๐
okay so real quick: this is the oxigraph-query(1) page from the General Commands Manual, and I'm about to make it make sense. pull up a chair, grab a boba, we're doing SPARQL today ๐งโจ
๐ธ NAME ๐ธ
oxigraph-query โ run a SPARQL query against the store. that's it. that's the whole vibe. ๐
โจ SYNOPSIS โจ
oxigraph query <-l|--location> [-q|--query] [--query-file]
[--query-base] [-r|--results-file] [--results-format] [--explain]
[--explain-file] [--stats] [--union-default-graph] [-h|--help]
๐ฆ DESCRIPTION ๐ฆ
Execute a SPARQL query against the store. literally the whole point of this command, no notes, she's an icon ๐
๐ OPTIONS ๐
-l,--location<LOCATION> โ the directory where Oxigraph data are persisted. this is where your stuff lives, your little data home ๐-q,--query<QUERY> โ the SPARQL query to execute. drop it right here, main character energy โจ
if no query or query file are given, stdin is used. so if you ghost both options, she'll just read from stdin, ngl ๐ซถ
--query-file<QUERY_FILE> โ a file in which the query is stored. your query, but make it a file ๐
same deal bestie: if no query or query file are given, stdin is used. ๐ซ
--query-base<QUERY_BASE> โ the base IRI of the query. the anchor point, the origin story, the it-girl of IRIs ๐-r,--results-file<RESULTS_FILE> โ the file in which the query results will be stored. where your results go to live their truth ๐
if no file is given, stdout is used. and in that case, the output format must be specified using the --format option. yes really, that's the rule, don't @ me ๐ญ
--results-format<RESULTS_FORMAT> โ the results format. can be an extension like"nt"or a MIME type like"application/n-triples"โ pick your fighter ๐
by default, the format is guessed from the results file extension. she's intuitive like that ๐ฎ
--explainโ print to stderr a human-readable explanation of the query evaluation. it's giving storytime but for your query ๐ฃ๏ธ
use the --stats option to print also query evaluation statistics. combo move, slay โจ
--explain-file<EXPLAIN_FILE> โ write to the given file an explanation of the query evaluation. explanation, but make it a whole document ๐
if the file extension is".json"the JSON format is used, if".txt"a human-readable format is used. she checks the extension, she's observant like that ๐
use the --stats option to print also query evaluation statistics. again. because it's important ๐ซถ
--statsโ compute some evaluation statistics to print as part of the query explanations. numbers! data! so satisfying ๐
beware, computing the statistics adds some overhead to the evaluation runtime. it's not free, bestie, it costs you time โณ
--union-default-graphโ if the SPARQL queries should look for triples in all the dataset graphs by default (ie. withoutGRAPHoperations). yes, all the graphs, noGRAPHrequired, she just knows ๐-h,--helpโ print help (see a summary with'-h'). the classic. the comfort option. she'll always be there for you ๐
that's the whole page, no cap, every single option accounted for, we ate and left no crumbs ๐
sign-off time: this gorgeous little page is the query entry in the oxigraph-query(1) manual, and it lives in the General Commands Manual section. date? not on this page bestie, she keeps it mysterious ๐
โจ
bye bye, go query something iconic ๐๐
๐ฆ where this page comes from
- nixos 26.05: oxigraph 0.5.7
- nixpkgs unstable: oxigraph 0.5.11
- ubuntu resolute: oxigraph 0.5.5+ds-2 ยท Apache-2.0 OR MIT
- ubuntu stonking: oxigraph 0.5.10+ds-1 ยท Apache-2.0 OR MIT
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms