oxigraph-query(1)

๐Ÿ“ฆ
version 0.5.10 ยท 2 versions
, in nixos 26.05, nixpkgs unstable, ubuntu resolute, ubuntu stonking

๐Ÿ’– 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. without GRAPH operations). yes, all the graphs, no GRAPH required, 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