RDF_VIEW_SYNC_TO_PHYSICAL — This function generates data synchronization triggers and/or actual RDF quad store data from transient Linked Data views. Basically, it enables you share physical and transient Linked Data views typically generated from 3rd party ODBC/JDBC accessible data sources.


RDF_VIEW_SYNC_TO_PHYSICAL ( in vgraph varchar ,
  in load_data int := 0 ,
  in pgraph varchar := null ,
  in transaction_mode int := 1 ,
  in atomicity int := 1 );


This function create new Transient and Materialized View pairs with option (where load = 1/0) to load data or wait for updates -- from triggers at execute time. 0 for non-transaction mode, and atomicity 0/1 determines server accessiblity where 1 indicates inaccessiblity during run. Note: applicable for Virtuoso 6.0 and higher.



The transient (or virutal) named graph to which synchronization triggers are to be associated, or the actual source of data used to populate a named graph in the quad store.


Flag that determines which operations are performed:

  • 0 -- only create synchronization triggers;

  • 1 -- create synchronization triggers and then immediately load data into a designated quad store named graph.


Designated quad store named graph IRI.


Integer values (0, 1, 2, or 3) which determine the transaction mode in place during synchronization. This is basically a call to log_enable () with the same values.


Enforces atomic mode during data synchronization. This mode of operation performs a checkpoint when completed, and is the recommended behavior for handling transient Linked Data views derived from large SQL large tables.

Return Types



Example 24.272. 

Example 1

Using the command-line iSQL utility or its variant hosted in the HTML based Conductor, and assuming named graphs denoted by the following IRIs:

  1. <> -- a named graph associated with virtual (and transient) RDF statements (triples) mapped to an ODBC accessible data source e.g., a "Customers" database.

  2. <urn:rdf:materialized:view:odbc:Customers> -- a named graph to be associated with RDF statements (triples) materialized from virtual triples in the designated source named graph.

SQL> RDF_VIEW_SYNC_TO_PHYSICAL ('', 1, 'urn:rdf:materialized:view:odbc:Customers');

# which is equivalent to:

SQL> RDF_VIEW_SYNC_TO_PHYSICAL ('', 1, 'urn:rdf:materialized:view:odbc:Customers', 1, 1);

Example 2

A variant of the prior example where with ACID transaction modality enabled:

SQL> RDF_VIEW_SYNC_TO_PHYSICAL ('', 0, 'urn:rdf:materialized:view:odbc:Customers', 1, 1);