This HTML5 document contains 30 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n16:this

foaf:made

n2:VirtTipsAndTricksGuideMergeOneByOne

Subject Item

n13:this

sioc:creator_of

n2:VirtTipsAndTricksGuideMergeOneByOne

Subject Item

n11:item

n12:services_of

n2:VirtTipsAndTricksGuideMergeOneByOne

Subject Item

n9:this

sioc:creator_of

n2:VirtTipsAndTricksGuideMergeOneByOne

Subject Item

n6:VOS

sioc:container_of

n2:VirtTipsAndTricksGuideMergeOneByOne

atom:entry

n2:VirtTipsAndTricksGuideMergeOneByOne

atom:contains

n2:VirtTipsAndTricksGuideMergeOneByOne

Subject Item

n2:VirtTipsAndTricksGuideMergeOneByOne

rdf:type

sioct:Comment atom:Entry

dcterms:created

2017-06-13T05:50:06.796467

dcterms:modified

2017-06-13T05:50:06.796467

rdfs:label

VirtTipsAndTricksGuideMergeOneByOne

foaf:maker

n8:this n16:this

dc:title

VirtTipsAndTricksGuideMergeOneByOne

opl:isDescribedUsing

n19:rdf

sioc:has_creator

n9:this n13:this

sioc:content

%META:TOPICPARENT{name="VirtTipsAndTricksGuide"}% ---+ What is the difference between a "merge" and a "one by one" execution of SPARQL queries across named graphs? By wrapping one or more triple patterns in a <b><code>GRAPH ?g { ... }</code></b> pattern, the triple patterns inside this "graph group pattern" will be restricted to the specified named graph, <b><code>?g</code></b>. Lacking the <b><code>GRAPH ?g { ... }</code></b>, the triples may be found in different named graphs. Using graph group patterns can thus dramatically reduce the amount of data to be processed for all triple patterns after the first in join order, so it's typically faster. <i><b>Note</b> -- The "default graph" in Virtuoso is not a union of all graphs; it is a sum. This means that Virtuoso's behavior differs slightly from the SPARQL spec, in that some duplicate result rows may appear if the same values appear as <code>{ ?s ?p ?o }</code> in two or more different graphs). (Results perfectly conforming to the SPARQL spec would leave out these duplicate rows.)</i> This query will deliver matching triples from any and all named graphs in the Virtuoso store -- <verbatim> [PREFIXes here] SELECT ?serial ?sr ?ct1 ?ct2 WHERE { ?sr a dm:SessionRecord . ?sr dm:hasDataSnapshot ?snap . ?device dm:hasSessionRecord ?sr . ?device dm:hasSerialNumber ?serial . [etc.] } </verbatim> With the added <b><code>GRAPH ?g { ... }</code></b> patterns below, only matching triples from the specified named graph(s) will be returned. <verbatim> [PREFIXes here] SELECT ?serial ?sr ?ct1 ?ct2 WHERE { GRAPH ?g1 { ?sr a dm:SessionRecord } GRAPH ?g2 { ?sr dm:hasDataSnapshot ?snap } GRAPH ?g3 { ?device dm:hasSessionRecord ?sr } GRAPH ?g4 { ?device dm:hasSerialNumber ?serial } [etc.] } </verbatim> ---++ Related * [[VirtTipsAndTricksGuide][Virtuoso Tips and Tricks Collection]] * [[http://www.w3.org/TR/rdf-sparql-query/][SPARQL Query Language for RDF]]

sioc:id

9b9e17756823a30648ec80c2b39ceccf

sioc:link

n2:VirtTipsAndTricksGuideMergeOneByOne

sioc:has_container

n6:VOS

n12:has_services

n11:item

atom:title

VirtTipsAndTricksGuideMergeOneByOne

sioc:links_to

n15:

atom:source

n6:VOS

atom:author

n16:this

atom:published

2017-06-13T05:50:06Z

atom:updated

2017-06-13T05:50:06Z

sioc:topic

n6:VOS