File: rdf_view_sync_to_physical.xml

package info (click to toggle)
virtuoso-opensource 7.2.5.1%2Bdfsg1-0.3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 285,240 kB
  • sloc: ansic: 641,220; sql: 490,413; xml: 269,570; java: 83,893; javascript: 79,900; cpp: 36,927; sh: 31,653; cs: 25,702; php: 12,690; yacc: 10,227; lex: 7,601; makefile: 7,129; jsp: 4,523; awk: 1,697; perl: 1,013; ruby: 1,003; python: 326
file content (127 lines) | stat: -rw-r--r-- 6,960 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
 -
 -  This file is part of the OpenLink Software Virtuoso Open-Source (VOS)
 -  project.
 -
 -  Copyright (C) 1998-2018 OpenLink Software
 -
 -  This project is free software; you can redistribute it and/or modify it
 -  under the terms of the GNU General Public License as published by the
 -  Free Software Foundation; only version 2 of the License, dated June 1991.
 -
 -  This program is distributed in the hope that it will be useful, but
 -  WITHOUT ANY WARRANTY; without even the implied warranty of
 -  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
 -  General Public License for more details.
 -
 -  You should have received a copy of the GNU General Public License along
 -  with this program; if not, write to the Free Software Foundation, Inc.,
 -  51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
 -
-->
<refentry id="fn_rdf_view_sync_to_physical">
  <refmeta>
    <refentrytitle>RDF_VIEW_SYNC_TO_PHYSICAL</refentrytitle>
    <refmiscinfo>rdf</refmiscinfo>
  </refmeta>
  <refnamediv>
    <refname>RDF_VIEW_SYNC_TO_PHYSICAL</refname>
    <refpurpose>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.</refpurpose>
  </refnamediv>
  <refsynopsisdiv>
    <funcsynopsis id="fsyn_rdf_view_sync_to_physical">
      <funcprototype id="fproto_rdf_view_sync_to_physical">
        <funcdef><function>RDF_VIEW_SYNC_TO_PHYSICAL</function></funcdef>
	<paramdef>in <parameter>vgraph</parameter> varchar</paramdef>
	<paramdef>in <parameter>load_data</parameter> int := 0</paramdef>
	<paramdef>in <parameter>pgraph</parameter> varchar := null</paramdef>
	<paramdef>in <parameter>transaction_mode</parameter> int := 1</paramdef>
  <paramdef>in <parameter>atomicity</parameter> int := 1</paramdef>
      </funcprototype>
    </funcsynopsis>
  </refsynopsisdiv>
  <refsect1 id="desc_rdf_view_sync_to_physical">
    <title>Description</title>
    <para>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.
    </para>
  </refsect1>
  <refsect1 id="params_rdf_view_sync_to_physical">
    <title>Parameters</title>
    <refsect2><title>vgraph</title>
      <para>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.</para>
    </refsect2>
    <refsect2><title>load_data</title>
      <para>Flag that determines which operations are performed:</para>
      <itemizedlist mark="bullet">
        <listitem>0 -- only create synchronization triggers;</listitem>
        <listitem>1 -- create synchronization triggers and then immediately load data into a designated quad store
        	named graph.
        </listitem>
      </itemizedlist>
    </refsect2>
    <refsect2><title>pgraph</title>
      <para>Designated quad store named graph IRI.</para>
    </refsect2>
    <refsect2><title>transaction_mode</title>
      <para>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.</para>
    </refsect2>
    <refsect2><title>atomicity</title>
      <para>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.</para>
    </refsect2>    
  </refsect1>
  <refsect1 id="ret_rdf_view_sync_to_physical"><title>Return Types</title>
    <para>any</para>
  </refsect1>
  <refsect1 id="examples_rdf_view_sync_to_physical">
   <title>Examples</title>
    <example id="ex_rdf_view_sync_to_physical"><title></title>
     <para>Example 1</para>
     <para>Using the command-line iSQL utility or its variant hosted in the HTML based Conductor, and assuming named
     	graphs denoted by the following IRIs:</para>
     <orderedlist>
       <listitem>&lt;http://www.openlinksw.com/schemas/odbcCustomers#&gt; -- a named graph associated with virtual (and transient)
       	 RDF statements (triples) mapped to an ODBC accessible data source e.g., a "Customers" database.
       </listitem>
       <listitem>&lt;urn:rdf:materialized:view:odbc:Customers&gt; -- a named graph to be associated with RDF statements (triples)
       	 materialized from virtual triples in the designated source named graph.
       </listitem>
     </orderedlist>
<screen><![CDATA[
SQL> RDF_VIEW_SYNC_TO_PHYSICAL ('http://www.openlinksw.com/schemas/odbcCustomers#', 1, 'urn:rdf:materialized:view:odbc:Customers');

# which is equivalent to:

SQL> RDF_VIEW_SYNC_TO_PHYSICAL ('http://www.openlinksw.com/schemas/odbcCustomers#', 1, 'urn:rdf:materialized:view:odbc:Customers', 1, 1);
]]></screen>
     <para>Example 2</para>
     <para>A variant of the prior example where with ACID transaction modality enabled:</para>
<screen><![CDATA[
SQL> RDF_VIEW_SYNC_TO_PHYSICAL ('http://www.openlinksw.com/schemas/odbcCustomers#', 0, 'urn:rdf:materialized:view:odbc:Customers', 1, 1);
]]></screen>
    </example>
  </refsect1>
  <refsect1 id="seealso_rdf_view_sync_to_physical">
    <title>See Also</title>
    <para><link linkend="fn_rdf_audit_metadata"><function>DB.DBA.RDF_AUDIT_METADATA()</function></link></para>
    <para><link linkend="fn_rdf_backup_metadata"><function>DB.DBA.RDF_BACKUP_METADATA()</function></link></para>
    <para><link linkend="fn_rdf_load_rdfxml_mt"><function>DB.DBA.RDF_LOAD_RDFXML_MT()</function></link></para>
    <para><link linkend="fn_ttlp"><function>DB.DBA.TTLP()</function></link></para>
    <para><link linkend="fn_ttlp_mt"><function>DB.DBA.TTLP_MT()</function></link></para>
    <para><link linkend="fn_rdf_triples_to_rdf_xml_text"><function>DB.DBA.RDF_TRIPLES_TO_RDF_XML_TEXT()</function></link></para>
    <para><link linkend="fn_sparql_rexec"><function>DB.DBA.SPARQL_REXEC()</function></link></para>
    <para><link linkend="fn_sparql_rexec_to_array"><function>DB.DBA.SPARQL_REXEC_TO_ARRAY()</function></link></para>
    <para><link linkend="fn_sparql_rexec_with_meta"><function>DB.DBA.SPARQL_REXEC_WITH_META()</function></link></para>
    <para><link linkend="fn_rdf_quad_uri"><function>DB.DBA.RDF_QUAD_URI()</function></link></para>
    <para><link linkend="fn_rdf_quad_uri_l_typed"><function>DB.DBA.RDF_QUAD_URI_L_TYPED()</function></link></para>
    <para><link linkend="fn_rdf_ttl2hash"><function>DB.DBA.RDF_TTL2HASH()</function></link></para>
  </refsect1>
</refentry>