<?xml version="1.0" encoding="ISO-8859-1" ?>
<!--ATOM based XML document generated By OpenLink Virtuoso-->
<atom:feed xmlns:atom="http://www.w3.org/2005/Atom">
<atom:id>http://docs.openlinksw.com/virtuoso/functions.html</atom:id>
<atom:title>Virtuoso Functions Guide</atom:title>
<atom:link href="http://docs.openlinksw.com/virtuoso/functions.html" type="text/html" rel="alternate" />
<atom:link href="http://docs.openlinksw.com/virtuoso/functions.html" type="application/atom+xml" rel="self" />
<atom:subtitle>OpenLink Virtuoso Universal Server: Documentation</atom:subtitle>
 <atom:author>
  <atom:name>virtuoso.docs@openlinksw.com</atom:name>
  <atom:email>virtuoso.docs@openlinksw.com</atom:email>
  </atom:author>
<atom:updated>2009-11-16T14:26:59Z</atom:updated>
<atom:generator>OpenLink Software Documentation Team</atom:generator>
<atom:logo>http://docs.openlinksw.com/virtuoso/../images/misc/logo.jpg</atom:logo>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_var.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_var.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAR</atom:title>
  <atom:content type="html">Returns the variance.VAR (VARIANCE) returns variance of expr. Virtuoso calculates the variance of expr as follows: 0 if the number of rows in expr = 1; VAR_SAMP if the number of rows in expr &gt; 1</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_var_samp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_var_samp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAR_SAMP</atom:title>
  <atom:content type="html">Returns the sample variance.VAR_SAMP returns the sample variance of a set of numbers after discarding the nulls in this set. The expr is a numeric expression, and the function returns a value of type NUMERIC. If the function is applied to an empty set, then it returns null. The function makes the following calculation: This function is similar to VAR, except that given an input set of one element, VAR returns 0 and VAR_SAMP returns null.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_var_pop.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_var_pop.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAR_POP</atom:title>
  <atom:content type="html">Returns the population variance.VAR_POP returns the population variance of a set of numbers after discarding the nulls in this set. The expr is a number expression, and the function returns a value of type NUMERIC. If the function is applied to an empty set, then it returns null. The function makes the following calculation:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_stddev.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_stddev.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: STDDEV</atom:title>
  <atom:content type="html">Returns the standard deviation.STDDEV returns standard deviation. it returns STDDEV_SAMP if the number of pairs is more than one, or NULL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_stddev_samp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_stddev_samp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: STDDEV_SAMP</atom:title>
  <atom:content type="html">Returns the cumulative sample standard deviation.STDDEV_SAMP computes the cumulative sample standard deviation and returns the square root of the sample variance. The expr is a numeric expression, and the function returns a value of type NUMERIC. This function is same as the square root of the VAR_SAMP function. When VAR_SAMP returns null, this function returns null.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_stddev_pop.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_stddev_pop.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: STDDEV_POP</atom:title>
  <atom:content type="html">Returns the population standard deviation.STDDEV_POP computes the population standard deviation and returns the square root of the population variance. This function is the same as the square root of the VAR_POP function. When VAR_POP returns null, this function returns null.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_syy.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_syy.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_SYY</atom:title>
  <atom:content type="html">Auxiliary function used to compute various diagnostic statistics.REGR_SYY makes the following computation after eliminating NULL (expr1, expr2) pairs:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_sxx.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_sxx.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_SXX</atom:title>
  <atom:content type="html">Auxiliary function used to compute various diagnostic statistics.REGR_SXX makes the following computation after eliminating NULL (expr1, expr2) pairs:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_sxy.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_sxy.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_SXY</atom:title>
  <atom:content type="html">Auxiliary function used to compute various diagnostic statistics.REGR_SXY makes the following computation after eliminating NULL (expr1, expr2) pairs:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_avgx.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_avgx.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_AVGX</atom:title>
  <atom:content type="html">Evaluates the average of the independent variable (expr2) of the regression line.REGR_AVGX evaluates the average of the independent variable (expr2) of the regression line. It makes the following computation after the elimination of null (expr1, expr2) pairs:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_avgy.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_avgy.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_AVGY</atom:title>
  <atom:content type="html">Evaluates the average of the independent variable (expr1) of the regression line.REGR_AVGY evaluates the average of the independent variable (expr1) of the regression line. It makes the following computation after the elimination of null (expr1, expr2) pairs:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_r2.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_r2.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_R2</atom:title>
  <atom:content type="html">Returns the coefficient of determination (R-squared) of the regression line.REGR_R2 returns the coefficient of determination (also called &quot;R-squared&quot; or &quot;goodness of fit&quot;) for the regression. VAR_POP(expr1) and VAR_POP(expr2) are evaluated after the elimination of null pairs. The return values are:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_count.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_count.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_COUNT</atom:title>
  <atom:content type="html">Returns the number of non-null numbers used to fit the regression line.REGR_COUNT Returns the number of non-null numbers used to fit the regression line.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_intercept.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_intercept.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_INTERCEPT</atom:title>
  <atom:content type="html">Returns the y-intercept of the regression line.REGR_INTERCEPT returns the y-intercept of the regression line. After the elimination of null (expr1, expr2) pairs, it makes the following computation:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regr_slope.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regr_slope.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REGR_SLOPE</atom:title>
  <atom:content type="html">Returns the slope of the line.REGR_SLOPE returns the slope of the line. After the elimination of null (expr1, expr2) pairs, it makes the following computation:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_covar_samp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_covar_samp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: COVAR_SAMP</atom:title>
  <atom:content type="html">Returns the sample covariance of a set of number pairs.COVAR_SAMP returns the sample covariance of a set of number pairs. Both expr1 and expr2 are numeric expressions. Virtuoso applies the function to the set of (expr1, expr2) pairs after eliminating all pairs for which either expr1 or expr2 is null. Then Virtuoso makes the following computation: where n is the number of (expr1, expr2) pairs where neither expr1 nor expr2 is null.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_covar_pop.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_covar_pop.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: COVAR_POP</atom:title>
  <atom:content type="html">Returns the population covariance of a set of number pairs.COVAR_POP returns the population covariance of a set of number pairs. Both expr1 and expr2 are numeric expressions. Virtuoso applies the function to the set of (expr1, expr2) pairs after eliminating all pairs for which either expr1 or expr2 is null. Then Virtuoso makes the following computation: where n is the number of (expr1, expr2) pairs where neither expr1 nor expr2 is null.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_corr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Aggregate Functions<atom:link href="http://docs.openlinksw.com/virtuoso/fn_corr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: CORR</atom:title>
  <atom:content type="html">Returns the coefficient of correlation of a set of number pairs.CORR returns the coefficient of correlation of a set of number pairs. Both expr1 and expr2 are number expressions. Virtuoso applies the function to the set of (expr1, expr2) after eliminating the pairs for which either expr1 or expr2 is null. Then Virtuoso makes the following computation:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_abs.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_abs.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: abs</atom:title>
  <atom:content type="html">Return the absolute value of a numberabs returns the absolute value of its argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn___any_grants.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn___any_grants.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: __any_grants</atom:title>
  <atom:content type="html">Checks a table for grants.The __any_grants() can be used to test whether there are any rights granted (for insert/update/delete) to a table for current SQL account.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_aref.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_aref.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: aref</atom:title>
  <atom:content type="html">returns specific element of an array or stringaref returns the nth element of an array, string or string_session, where nth is a zero-based index. If the first argument is a string or string_session, the integer ASCII value of the nth character is returned. If the first argument is an array of any, then the corresponding element is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ascii.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ascii.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ascii</atom:title>
  <atom:content type="html">Get ASCII value of a characterascii returns the ASCII value of the first character of a string. If an empty string is given, then zero is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_aset.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_aset.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: aset</atom:title>
  <atom:content type="html">set array elementaset sets the nth element of a string, array or vector where nth is a zero-based index. If the first argument is a string, the nth character of string is replaced with the ASCII value given in the third argument elem.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_atof.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_atof.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: atof</atom:title>
  <atom:content type="html">Convert a string to single precision floatatof returns its argument as a single precision floating point. If the string cannot be parsed and converted to a valid float, a value 0.0 is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_atoi.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_atoi.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: atoi</atom:title>
  <atom:content type="html">Convert a string to an integeratoi returns its argument as an integer. If the string cannot be parsed and converted to a valid integer, a value 0 is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_att_local_name.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_att_local_name.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: att_local_name</atom:title>
  <atom:content type="html">Compose a fully qualified table name based on DSN and remote table name.The utility function, att_local_name(), can be used to make a fully qualified table name from non-qualified or qualified one, i.e. the qualifier and owner will be added if they are missing. The schema name will be replaced with current qualifier on execution, owner will be replaced or added with name of supplied DSN name. All non-alphanumeric characters in the name will be replaced with underscore symbol.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_backup.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Backup<atom:link href="http://docs.openlinksw.com/virtuoso/fn_backup.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: backup</atom:title>
  <atom:content type="html">Write data into transaction log format for backup purposes. Deprecated. This function requires dba privileges.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_backup_online.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Backup<atom:link href="http://docs.openlinksw.com/virtuoso/fn_backup_online.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: backup_online</atom:title>
  <atom:content type="html">perform online backup of databaseThis procedure will backup all information from the checkpoint space to a series of files named &quot;&lt;file_prefix&gt;&lt;n&gt;.bp&quot;, where &lt;n&gt; is the sequence number of the file in the backup series. The first backup will be a full gzip compressed dump of database pages in the checkpoint space. Any subsequent call will only backup pages which have changed since the last backup was made. To start with a fresh full backup, use backup_clear_context to clear the change tracking data. At each checkpoint the checkpoint space will be updated, and the next &quot;backup_online;&quot; procedure will create new files. Once backup_online() has been called for the first time, the arguments supplied will be used for subsequent calls to it. Hence, arguments supplied to this procedure (except the &quot;dirs&quot; argument) will be ignored in subsequent calls. Before a new backup series can be started, the backup_context_clear(); procedure must be called first. This procedure will clear the current backup context and mark all pages in the checkpoint space as ready for backup. A database checkpoint cannot be performed while an online backup is in progress. Attempt to do a checkpoint will wait until the backup is complete.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_backup_context_clear.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Backup<atom:link href="http://docs.openlinksw.com/virtuoso/fn_backup_context_clear.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: backup_context_clear</atom:title>
  <atom:content type="html">Clears the backup context and marks all pages in checkpoint space as ready for online backupThis procedure must be called before a new backup series can be started, This procedure will clear the current backup context and mark all pages in the checkpoint space as ready for backup.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_bif_arg.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Server Extension Interface (VSEI)<atom:link href="http://docs.openlinksw.com/virtuoso/fn_bif_arg.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: Virtuoso Server Extension Interface (VSEI) functions</atom:title>
  <atom:content type="html">Get parameters for built in functionThe bif_...._arg functions are used in the Virtuoso shared object. They allow customization of the Virtuoso server. They are written in C code, and linked with the Virtuoso shared object. The _or_null_ variants of these functions represent the SQL null value as a 00 pointer, even though getting the same argument with bif_arg() would return a box with the DV_DB_NULL tag. All number functions will coerce other types of numbers to the result type. All array argument functions will accept any type of array. It is up to the VSE itself to distinguish. Virtuoso Server Extensions (VSEs) were formally referred to as Built-In Functions (BIFs).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_bit_and.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_bit_and.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: bit_and</atom:title>
  <atom:content type="html">Returns bitwise AND of two 32-bit integers.The function returns bitwise AND of two given integers. On 64-bit platforms, both arguments are intentionally truncated to 32 bits to maintain compatibility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_bit_or.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_bit_or.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: bit_or</atom:title>
  <atom:content type="html">Returns bitwise OR of two 32-bit integers.The function returns bitwise OR of two given integers. On 64-bit platforms, both arguments are intentionally truncated to 32 bits to maintain compatibility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_bit_not.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_bit_not.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: bit_not</atom:title>
  <atom:content type="html">Returns bitwise NOT of a 32-bit integer.The function returns bitwise NOT of a given integer. On 64-bit platforms the argument is intentionally truncated to 32 bits to maintain compatibility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_bit_shift.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_bit_shift.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: bit_shift</atom:title>
  <atom:content type="html">Returns the result of bitwise shift operation over two 32-bit integers.The function returns bitwise shift of two given integers. Depending on the arguments, the shift may be left or right. For right-shift, leftmost bits of the result are filled by the value of the 31-st bit. On 64-bit platforms, both arguments are intentionally truncated to 32 bits and the shift is restricted to 32 bits to maintain compatibility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_bit_xor.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_bit_xor.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: bit_xor</atom:title>
  <atom:content type="html">Returns bitwise XOR (exclusive &quot;or&quot;) of two 32-bit integers.The function returns bitwise XOR (exclusive &quot;or&quot;) of two given integers. On 64-bit platforms, both arguments are intentionally truncated to 32 bits, to provide compartibility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_blob_to_string.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_blob_to_string.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: blob_to_string</atom:title>
  <atom:content type="html">Convert a blob to stringAlthough primarily used for converting blobs (long varbinary, long varchar) to string, blob_to_string may also be used to convert from wide string, persistent XML (XPER) and string_output streams. If the data being converted is longer than maximum length of a string, blob_to_string will signal an error.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_blob_to_string_output.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_blob_to_string_output.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: blob_to_string_output</atom:title>
  <atom:content type="html">Convert a blob to string sessionAlthough primarily used for converting blobs (long varbinary, long varchar) to string output object, blob_to_string_output may also be used to convert from wide string, persistent XML (XPER) and string_output streams.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_bookmark.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Cursor<atom:link href="http://docs.openlinksw.com/virtuoso/fn_bookmark.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: bookmark</atom:title>
  <atom:content type="html">Return the bookmark for current row of a scrollable cursorbookmark returns a bookmark for the current row of an open scrollable cursor. Given an invalid argument, i.e. no cursor, no current row or non-open cursor, it signals an error. The returned value can be used in subsequent FETCH .. BOOKMARK over the same cursor.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ceiling.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ceiling.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ceiling</atom:title>
  <atom:content type="html">Round a number to positive infinity.ceiling calculates the smallest integer greater than or equal to x.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cfg_item_count.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cfg_item_count.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cfg_item_count</atom:title>
  <atom:content type="html">return number of items in a section in configuration fileReturn the number of items that exist in the specified section of the INI file.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cfg_item_name.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cfg_item_name.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cfg_item_name</atom:title>
  <atom:content type="html">get nth item name from ini fileReturns the name of the item specified by item_index (begins from zero). If the index and section name do not point to a valid item, then zero is returned, otherwise on success the function returns the item name.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cfg_item_value.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cfg_item_value.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cfg_item_value</atom:title>
  <atom:content type="html">returns the value of an item from the ini fileReturn the value of an item identified by item_name and section parameters from the specified INI file.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cfg_section_count.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cfg_section_count.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cfg_section_count</atom:title>
  <atom:content type="html">get number of sections in an INI fileReturns the number of sections in an INI file.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cfg_section_name.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cfg_section_name.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cfg_section_name</atom:title>
  <atom:content type="html">returns INI file section nameReturns the name of section specified by the index (begins from zero). If the index can reference a section, the that section name is returned, otherwise returns zero on error.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cfg_write.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cfg_write.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cfg_write</atom:title>
  <atom:content type="html">Writes the item=value to an INI fileThis function requires dba privileges. This function allows modification of existing entries, or update updating existing items in an INI file.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_charset_define.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_charset_define.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: charset_define</atom:title>
  <atom:content type="html">Define a character set.This function creates a new narrow language-specific character set, or redefines an existing one.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_charset_recode.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_charset_recode.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: charset_recode</atom:title>
  <atom:content type="html">Translate a string to another character setThis function translates a string from a given source charset to a destination charset. It provides a generic way of recoding string entities. The src_charset may be a narrow or a wide string. If it&#39;s a narrow string (VARCHAR) then the src_charset is taken into account and defines the current encoding of the src_string. In any other case src_charset is ignored. src_charset and dst_charset are names of system-defined 8 bit charset tables. Use charsets_list to obtain a list of currently defined character sets and aliases. If either of these is null, then the charset in effect is used. There are two special character set names - &quot;UTF-8&quot; and &quot;_WIDE_&quot; - that are recognized by this function. These represent UTF-8 encoding of characters and wide string (NVARCHAR).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_charsets_list.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_charsets_list.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: charsets_list</atom:title>
  <atom:content type="html">List known character set names and aliases.This function produces a list of all character set names and aliases known to Virtuoso. The returned value is an array of strings with a character set name as each element. If the gen_res_set flag is 1, the function also produces a result set in which each row contains one varchar column with a name of a character set or alias.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_checkpoint_interval.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_checkpoint_interval.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: checkpoint_interval</atom:title>
  <atom:content type="html">Configure database checkpointingThis function changes the database checkpointing interval to the given value in minutes. It may also be used to disable checkpointing in two ways: By setting checkpoint interval to 0, the checkpoint will only be performed after roll forward upon database startup. A setting of -1 will disable all checkpointing. Main use for this function is to ensure a clean online backup of the database slices. Copying of the database may take long and checkpointing would modify those files in mid-copy, thus rendering the resulting copy unusable. In case the system should, for some reason or another, become unstable, it is sometimes better to disable checkpointing after a database restart to resume backing up from where it was left prior to a system crash. Disabling all checkpointing by giving checkpoint_interval the value of -1 will do just that. The interval setting will be saved in the server configuration file as value of CheckpointInterval in section [Parameters], thus it will persist over consecutive server shutdown/restart cycles. A long checkpoint_interval setting will produce longer transaction logs, which in turn prolongs the time it takes for the database to perform a roll forward upon restart in case it was shut down without making a checkpoint.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_chr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_chr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: chr</atom:title>
  <atom:content type="html">Convert a long character code to a character or wide characterchr returns a new one character long string containing the character with character code given as parameter.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_client_attr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_client_attr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: client_attr</atom:title>
  <atom:content type="html">returns a varchar containing the requested information from the connection</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_collation_define.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_collation_define.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: collation_define</atom:title>
  <atom:content type="html">define a new collationThis function lets you define a new collation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_complete_table_name.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_complete_table_name.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: complete_table_name</atom:title>
  <atom:content type="html">Returns a fully qualified table name.The complete_table_name() can be used to make a fully qualified table name from non-qualified one, i.e. the qualifier and owner will be added if they are missing.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_composite.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_composite.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: composite</atom:title>
  <atom:content type="html">create a composite objectCreate a composite object Returns a composite object containing the serialization of each argument. The total serialized length of the arguments may not exceed 255.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_composite_ref.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_composite_ref.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: composite_ref</atom:title>
  <atom:content type="html">get member of a composite objectcomposite_ref returns the nth element of the composite. The index is 0 based.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_concat.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_concat.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: concat</atom:title>
  <atom:content type="html">Concatenate stringsconcat returns a new string, concatenated from a variable number of strings given as arguments. NULL arguments are handled as empty strings. concat (str) returns a copy of str. concat () returns an empty string.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_concatenate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_concatenate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: concatenate</atom:title>
  <atom:content type="html">concatenate stringsConcatenate is an alias of concat.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_connection_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_connection_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: connection_get</atom:title>
  <atom:content type="html">Get connection variableconnection_get is used to retrieve values stored within the current connection context. See connection_set for a more detailed discussion of connection variables.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_connection_id.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_connection_id.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: connection_id</atom:title>
  <atom:content type="html">get connection identifierThis function returns a string uniquely identifying the connection in this server instance. It is usually a combination of server&#39;s port number and a serial number of the client.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_connection_is_dirty.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_connection_is_dirty.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: connection_is_dirty</atom:title>
  <atom:content type="html">check if current session connection variables have been alteredThis function is used to determine if the session variables have changed between a call to connection_vars_set and current point of execution. A call to connection_vars_set will cause subsequent calls to connection_is_dirty to return true. The function is useful in postprocessing functions for making conditional storage of session variables in a database table.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_connection_set.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_connection_set.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: connection_set</atom:title>
  <atom:content type="html">Associates a value to the name in the context of the present connectionThis associates a value to the name in the context of present connection. The name should be a string and the value can be any data type except blob, open cursor or an XML entity. If the value is an array it may not contain the restricted types. Connection variable setting is not logged and information stored will be lost when the connection is closed. The value can be retrieved by any future statement executing within the same connection. Connection variables can be used as a global variable mechanism for stored procedures, the scope being the client connection. In the case of VSP or SOAP this mechanism cannot be used to pass information between requests by the same client. It will however, be useful for having &#39;global variables&#39; between procedures called within the same HTTP request. Note that this mechanism is used to provide persistent HTTP session variables in some cases but this works through special before and after code which stores the values set with this function into an external session structure. In this sense this function itself has nothing to do with web session management although it can be used as a component for such.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_connection_vars.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_connection_vars.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: connection_vars</atom:title>
  <atom:content type="html">Retrieve all connection variables This function returns all stored session variables in an array with name/value pairs. Connection variables do not persist across sessions, one may maintain persistence of variables by storing them in a database table: see the Session Variables Section.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_connection_vars_set.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_connection_vars_set.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: connection_vars_set</atom:title>
  <atom:content type="html">set all connection variablesThis function clears all connection variables for current session and sets new ones defined in the array passed as parameter. Connection variables do not persist across sessions, one may maintain persistence of variables by storing them in a database table, as discussed in Session Variables -section.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_contains.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_contains.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: contains</atom:title>
  <atom:content type="html">A text contains predicate This is a SQL predicate that specifies a condition on a column on which a free text index exists. The expression is a string matching the grammar of a text search expression. This is computed for each evaluation of the contains predicate and does not have to be a constant. For example a parameter or variable of a containing score (e.g. procedure) is accepted. The score_limit is optional. If specified, it should be a numeric expression determining the minimum score required to produce a hit. A virtual column named &#39;SCORE&#39; is available in queries involving a contains predicate. This can for example be returned in a result set or used for sorting. Note that the name is in upper case and is case sensitive in all case modes.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cov_load.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cov_load.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cov_load</atom:title>
  <atom:content type="html">Load test coverage data from file.This function accepts one argument with name of file containing test coverage data. The expected format of the file is described in the Branch Coverage section. The loaded file is merged with the data already collected by Virtuoso. More than one file can be loaded. The ultimate report will be the union of all files.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cov_report.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cov_report.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cov_report</atom:title>
  <atom:content type="html">Produce a text coverage report.This function is used to produce a coverage report in text format. The format of the file is described in the Branch Coverage section. This function takes a filename &#39;fname&#39; as a path to the extended coverage report file and &#39;outdir&#39; as a path to a directory where .cov files will be stored. The profile.prof file in the output directory is a summary of function call counts and execution times, once ranked by self time, once by time spent inside the function and functions called from there. Note that directory must exists before calling this function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_cov_store.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_cov_store.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: cov_store</atom:title>
  <atom:content type="html">Writes a test coverage to a file.This function is used to produce a coverage file called fname. The expected format of the file is described in the Branch Coverage section. By default a normal concise coverage will be produced. If the add_comment parameter is set to 1 then the coverage will include code excerpts contained in line entities.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_createXML.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_createXML.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: createXML</atom:title>
  <atom:content type="html">This function creates an XMLType instance. It works absolutely identically to the XMLType() constructor and is provided solely for compatibility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_curdate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_curdate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: curdate</atom:title>
  <atom:content type="html">get current date and timeThese functions return the current date or time as a date, time or datetime, respectively. Internally they all return the same value but data type reported to client differs.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_current_charset.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_current_charset.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: current_charset</atom:title>
  <atom:content type="html">Get name of current charset.This function returns the &quot;preferred&quot; name of the current charset as a string. It returns value which is set in the INI file or those which is set with &#39;SET CHARSET=..&#39; call. This cannot be used to return charset for the current HTTP connection in the VSP or VSPX context.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vacuum.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vacuum.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.VACUUM</atom:title>
  <atom:content type="html">Compact the databaseThis function reads through the specified tables and indices and finds groups of adjacent pages holding data that will fit on fewer pages than it currently occupies. If such a compression can be made, the pages are thus compacted. The pages become part of the committed state and will be written to the checkpoint space on the next checkpoint. The vacuum operation is non-locking and can be run on a busy database. It will simply skip pages with ongoing activity such as pending cursors or locks. The vacuum procedure returns only after it has read through the indices it affects but it will not prevent other activity on the indices. The vacuum operation may run out of disk space even if it makes net gains because the modified pages will not be final until the next checkpoint and the originals will not be free until this same checkpoint. Thus manually running a checkpoint after vacuum runs out of space will free the space and vacuum may be rerun.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dateadd.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dateadd.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dateadd</atom:title>
  <atom:content type="html">arithmetic add to a datedateadd adds a positive or negative quantity of units to a date (in the internal date time format), and returns a new date so formed. The unit is specified as a string and can be one of the following: &#39;second&#39;, &#39;minute&#39;, &#39;hour&#39;, &#39;day&#39;, &#39;month&#39;, or &#39;year&#39;. Use datestring to convert the result to a human-readable string.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_datediff.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_datediff.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: datediff</atom:title>
  <atom:content type="html">get difference of 2 datesdatediff subtracts date1 from date2 and returns the difference as an integer in the specified units.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_datestring.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_datestring.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: datestring, datestring_gmt,</atom:title>
  <atom:content type="html">convert a datetime from internal to external date-time representationdatestring and datestring_gmt convert timestamps or datetimes from internal to external date-time representation. The external representation is a human-readable ASCII string of up to 30 characters. The external format is: YYYY-MM-DD hh:mm:ss uuuuuu where uuuuuu represents microseconds.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_datestring_gmt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_datestring_gmt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: datestring_GMT</atom:title>
  <atom:content type="html">convert a timestamp to external format string in GMTConverts the local datetime to GMT and returns its external representation as a string.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dav_api_add.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dav_api_add.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DAV add &amp; update functions</atom:title>
  <atom:content type="html">functions for adding, updating, deleting of DAV collections or resourcesDAV_COL_CREATE creates a new collection on path, with supplied security permissions, returning a collection id (COL_ID) upon success. DAV_RES_UPLOAD creates or replaces an existing resource on path with content, mime type and supplied security permissions. Returns a resource id (RES_ID) on success. DAV_DELETE Removes an existing collection/resource. If silent is set to a nonzero value, no errors codes will be returned. returns 1 on success.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dav_api_change.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dav_api_change.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DAV manipulation functions</atom:title>
  <atom:content type="html">Functions for manipulating an existing DAV collection or resourceDAV_COPY copies the resource or collection taken from path to the destination. returns COL_ID or RES_ID on success. DAV_MOVE moves the collection or resource to the destination path returns 1 on success. DAV_PROP_SET defines or updates the property with name propname with propvalue. Returns PROP_ID on success.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dav_api_lock.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dav_api_lock.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DAV lock manipulation functions</atom:title>
  <atom:content type="html">Operations on locks of DAV collections and resourcesDAV_LOCK sets a new lock or refresh an existing lock or creates a lock object. DAV_UNLOCK releases a lock. DAV_IS_LOCKED reports whether the resource or collection is locked.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dav_api_search.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dav_api_search.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DAV search functions</atom:title>
  <atom:content type="html">Functions for searching a DAV collection or resourceDAV_SEARCH_ID() returns the RES_ID or COL_ID, depending on the &#39;what&#39; parameter passed. (&#39;R&#39;esource or &#39;C&#39;ollection or &#39;P&#39;arent collection). DAV_SEARCH_PATH() returns full path string of resource or collection, depending on parameter passed. (&#39;R&#39;esource or &#39;C&#39;ollection or &#39;P&#39;arent collection). DAV_DIR_LIST() returns an array of arrays that contains the following information about the requested path:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dav_api_user.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dav_api_user.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: WebDAV Users &amp; Groups administration</atom:title>
  <atom:content type="html">Functions for manipulating an existing DAV collection or resourceDAV_ADD_USER() create a new WebDAV user with login name &#39;uid&#39; and password &#39;pwd&#39;. User will belong to the group named &#39;gid&#39;. &#39;perms&#39; are the default user permissions for creation of new resources. Additional user info supplied is &#39;home&#39; directory, &#39;full name&#39; and &#39;e-mail&#39;. DAV_DELETE_USER() remove the existing webDAV user named &#39;uid&#39;. DAV_HOME_DIR() returns the home folder for specified WebDAV user named &#39;uid&#39;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dav_exp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dav_exp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DAV_EXP</atom:title>
  <atom:content type="html">Export a retrieved Web site to another WebDAV enabled serverThis function is used to export local content retrieved from a Web Robot Copy to the local file system.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dayname.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dayname.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dayname</atom:title>
  <atom:content type="html">decompose a datetime to its componentsThese functions decompose a datetime to its components. These can be used on timestamps, datetimes, dates and times, all being the same internal data type.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dayofmonth.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_dayofmonth.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dayofmonth</atom:title>
  <atom:content type="html">get day of month from a datetimedayofmonth takes a datetime and returns an integer containing day of the month represented by the datetime</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dayofweek.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_dayofweek.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dayofweek</atom:title>
  <atom:content type="html">get day of week from a datetimedayofweek takes a datetime and returns an integer containing a number representing the day of week of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dayofyear.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_dayofyear.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dayofyear</atom:title>
  <atom:content type="html">get day of year from a datetimedayofyear takes a datetime and returns an integer containing a number representing the day of year of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dbg_obj_print.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dbg_obj_print.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dbg_obj_print</atom:title>
  <atom:content type="html">print to the Virtuoso system consoledbg_obj_print prints a variable number of arguments onto the system console (stdout) of Virtuoso server, each argument in its own native format, on the same line, which is followed by one newline.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dbg_printf.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dbg_printf.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dbg_printf</atom:title>
  <atom:content type="html">print formatted output onto the system consoledbg_printf prints a variable number (max. eight) of arguments to the system console of Virtuoso server, each argument formatted in C printf style, according to the format string specified in the first argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dbname.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dbname.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dbname</atom:title>
  <atom:content type="html">get current catalogReturns the current qualifier as set by the USE statement or default.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_delay.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_delay.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: delay</atom:title>
  <atom:content type="html">sleep for n secondsThis will halt calling procedure execution for specified interval in seconds.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dict_duplicate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Dictionary Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dict_duplicate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dict_duplicate</atom:title>
  <atom:content type="html">Creates a copy of the given dictionary.The function creates a full copy of the given dictionary. Dictionary objects are always passed by reference, even if dictionary is passed as an &#39;in&#39; argument of a function. If value of a variable is a dictionary and it is assigned to other variable then both variables refer to the same internal hash table. This function returns a really independent dictionary object. This function duplicates the given dictionary but does not duplicate dictionaries that may be stored in key-value pairs.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dict_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Dictionary Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dict_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dict_get</atom:title>
  <atom:content type="html">Returns the dependent part that corresponds to the given key in the given dictionary.The function returns the dependent part that corresponds to the given key in the given dictionary. The function returns default_value if the dictionary does not contain a pair whose key is equivalent to the given one. When only two arguments are passed to the function the default value is integer zero.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dict_list_keys.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Dictionary Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dict_list_keys.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dict_list_keys</atom:title>
  <atom:content type="html">Returns an array of all keys stored in the given dictionary.The function returns an array of all keys stored in the given dictionary, ignoring dependent parts of key-value pairs. This is especially useful when dictionary is used to form a set of distinct keys, when dependent parts are fake (typically zeroes). If the destructive parameter is nonzero then the function may avoid copying of keys to the resulting array by moving them out from the dictionary. This is faster but the dictionary will become empty at the end of operation. The destructive parameter does not have any effect if the dictionary is used as a value of more than one variable. Thus it is safe to make this parameter nonzero as soon as the variable passed to the function as dict is no longer in use after the function call and there&#39;s no need to inspect the whole program to check if other variables may be affected.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dict_new.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Dictionary Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dict_new.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dict_new</atom:title>
  <atom:content type="html">Creates a new dictionary to store key-value pairs.This function creates a new dictionary. A dictionary is a memory-resident hash table that can store an arbitrary number of key-value pairs. Both key and dependent part can be of any type, including vectors. Two keys of different data types are always considered as different even if SQL &#39;=&#39; operator return &#39;true&#39;, e.g. integer zero and double precision 0.0 are two different keys. Vectors are equivalent if their corresponding members are either equal scalars or equivalent vectors. XML entities are equivalent if they refer to the same node or attribute in the same document. Dictionary objects are always passed by reference, even if dictionary is passed as an &#39;in&#39; argument of a function. If value of a variable is a dictionary and it is assigned to other variable then both variables refer to the same internal hashtable. To create two really independent dictionary objects, use dict_duplicate ().</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dict_put.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Dictionary Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dict_put.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dict_put</atom:title>
  <atom:content type="html">Adds a key-value pair to a dictionaryThe function adds or updates a key-value pair in the given dictionary. If the dictionary contains a pair with the key part equivalent to the given one then old value is replaced with a new one. Otherwise, a new pair is added to the dictionary.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dict_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Dictionary Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dict_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dict_remove</atom:title>
  <atom:content type="html">Removes the given key and associated dependent value from the given dictionary.The function removes the given key and the associated dependent value from the given dictionary. If the key-value pair is found (and removed) the function returns 1. If the dictionary does not contain a key equivalent to the given one the function returns zero.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dict_to_vector.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Dictionary Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dict_to_vector.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dict_to_vector</atom:title>
  <atom:content type="html">Returns a get_keyword style vector of all items stored in the given dictionary.The function returns an array of all data stored in the given dictionary, every pair is represented as two consecutive element of the resulting array. Thus the dictionary of N pairs is converted into a vector of length 2N where keys are at positions 0, 2, 4, ..., 2N-1 and corresponding dependent data are at positions 1, 3, 5, ..., 2N. If keys are all scalars of same type then get_keyword function can be used to search in the resulting array. If the destructive parameter is nonzero then the function may avoid copying of keys to the resulting array by moving them out from the dictionary. This is faster but the dictionary will become empty at the end of the operation. The destructive parameter does not have any effect if the dictionary is used as a value of more than one variable. Thus it is safe to make this parameter nonzero as soon as the variable passed to the function as dict is no longer in use after the function call and there&#39;s no need to inspect the whole program to check if other variables may be affected.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_disconnect_user.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_disconnect_user.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: disconnect_user</atom:title>
  <atom:content type="html">Disconnect client connections of a given userdisconnect_user disconnects clients whose username matches the username_pattern string given as an argument, and returns an integer value giving the number of clients disconnected. This can be used after DELETE USER or REVOKE statement to make sure that the affected user has no open connections.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dt_set_tz.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dt_set_tz.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dt_set_tz</atom:title>
  <atom:content type="html">modifies the timezone component of a datetimeThis modifies the timezone component of a datetime. The value remains equal for purposes of comparison but will look different when converted to a string. The timezone component is an offset from UTC in minutes. It can be retrieved with the timezone function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dvector.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dvector.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dvector</atom:title>
  <atom:content type="html">return an array of either long, float or double These functions are like vector but return an array of either long, float or double whereas vector returns a generic, untyped array.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_end_result.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_end_result.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: end_result</atom:title>
  <atom:content type="html">End the current result set.The result_names() predefines variables to be used in a result set to follow. The variables must be previously declared, from which the column data types are ascertained. This assigns the meta data but does not send any results. The result() function sends its parameters as a single row of results. These parameters should be compatible with those in the previous result_names(). The end_result() function can be used to separate multiple result sets. The result_names() can then be used to alter the result set structure. The result_names() call can be omitted if the application already knows what columns and their types are to be returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_either.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_either.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: either</atom:title>
  <atom:content type="html">conditionally return one of specified parameterseither returns a copy of arg1 if cond is something else than integer 0 (zero). Otherwise, a copy of arg2 is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_elh_get_handler.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_elh_get_handler.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: elh_get_handler</atom:title>
  <atom:content type="html">get localization function handler</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_elh_load_handler.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_elh_load_handler.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: elh_load_handler</atom:title>
  <atom:content type="html">load encoding handler into system Loads given handler in table of handlers bound to encoding specified in the handler, using ISO 639 and RFC 1766 language IDs of the handler as keys for future table lookups. If another handler was already specified for given RFC 1766 id, table entry will be updated and will refer to new handler. If another handler was already specified for given ISO 639 id, it will be replaced only if new handler has ISO 639 language ID equal to its RFC 1766 ID. Please do not load custom versions of &#39;x-any&#39; and &#39;x-ftq-x-any&#39; handlers.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_encode_base64.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Encoding &amp; Decoding<atom:link href="http://docs.openlinksw.com/virtuoso/fn_encode_base64.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: encode_base64</atom:title>
  <atom:content type="html">base64-encode/decode a stringThese functions convert strings from/to base64-encoding.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_equ.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_equ.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: equ</atom:title>
  <atom:content type="html">comparison functionsThese functions return 1 if their first argument is less than (lt), less than or equivalent (lte), greater than (gt), greater than or equivalent (gte), equivalent (equ), or not equivalent (neq) to the second argument, respectively. If the arguments are not of the same type, then an appropriate type coercion is done for them before comparison. These functions correspond to SQL query operators &lt;, &lt;=, &gt;, &gt;=, = and &lt;&gt; and are needed because the SQL syntax does not allow these operators to be used on the left side of FROM keyword in a SELECT statement.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exec.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exec.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: exec</atom:title>
  <atom:content type="html">dynamic execution of SQL returning state and result setThis function provides dynamic SQL capabilities in Virtuoso PL. The first argument is an arbitrary SQL statement, which may contain parameter placeholders. The function returns as output parameters a SQL state, error message, column metadata and result set rows if the statement is a select. A stored procedure can be invoked by exec but a procedure&#39;s result set will not be received in the rows output parameter but rather sent to the client.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exec_close.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exec_close.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: close</atom:title>
  <atom:content type="html">Closes cursor created by exec()Closes the cursor opened by the exec() function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exec_next.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exec_next.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: exec_next</atom:title>
  <atom:content type="html">Get next result from a result setUse exec_next() to iterate over a result set produced by a statement run with exec.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exec_result.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exec_result.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: exec_result</atom:title>
  <atom:content type="html">Returns a result set row to the calling procedure contextThis function returns a result set row to the calling procedure&#39;s context, whether it is the client, exec function or a procedure view). The row&#39;s values are the elements of the supplied res_values_array vector.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exec_result_names.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exec_result_names.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: exec_result_names</atom:title>
  <atom:content type="html">Supplies column details for procedure result set output.This function allows you to define the column details for result sets returned by procedures, in particular for use with the exec() function. This function is similar to result_names().</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exec_metadata.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exec_metadata.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: exec_metadata</atom:title>
  <atom:content type="html">Compiles a SQL statement and returns the metadataThis function provides dynamic SQL capabilities in Virtuoso PL. The first argument is an arbitrary SQL statement, which may contain parameter placeholders. The function returns as output parameters a SQL state, error message, column metadata if the statement is a select.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exec_score.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exec_score.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: exec_score</atom:title>
  <atom:content type="html">Compiles a SQL statement and returns the estimate time costThis function provides dynamic SQL capabilities in Virtuoso PL. The first argument is an arbitrary SQL statement, which may contain parameter placeholders. The function returns as output parameters a SQL state, error message and returns the estimate time cost in milliseconds.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_exp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_exp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: exp</atom:title>
  <atom:content type="html">calculate exponentThe function raises e to the power of x, it works with double precision floating point numbers, converts its argument to an IEEE 64-bit float and returns a result of that type.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_explain.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_explain.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: explain</atom:title>
  <atom:content type="html">describe SQL statement compilation The explain function compiles a SQL statement and returns a description of that compilation as a result set, return value or parse tree. The result set consists of one VARCHAR column with one line of the description in each row. Any given line may be quite long, even several hundred characters. The output is not a complete disassembly of the query graph, but it is detailed enough to show the join order, the sub-query structure, and the order of evaluation of query predicates, as well as the splitting of a distributed VDB query over different data sources. The optional cursor type can be one of the SQL_CURSOR_&lt;xx&gt; constants, or one of the special values listed below. The default is 0, for FORWARD ONLY. The special values each have special effect, as listed. If the statement is a SELECT and the cursor type is not FORWARD ONLY, the auxiliary SQL statements used by the cursor implementation are shown.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_delete.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_delete.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_delete</atom:title>
  <atom:content type="html">Delete a file from the file systemThis function requires dba privileges. This function is used to delete a file from file system. This function has a silent mode, where no errors will be signalled upon failure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_dirlist.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_dirlist.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_dirlist</atom:title>
  <atom:content type="html">Returns list with content of file system directoryThis function requires dba privileges. This returns the list of the contents of a given file system directory.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_mkdir.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_mkdir.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_mkdir</atom:title>
  <atom:content type="html">Creates a directory in the file systemThis function requires dba privileges. This function creates a file system directory.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_mkpath.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_mkpath.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_mkpath</atom:title>
  <atom:content type="html">Make a directory chainThis function requires dba privileges. This is to create a directory chain i.e. &#39;a/b/c/d&#39;, where one or more elements in the path may not exist.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_stat.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_stat.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_stat</atom:title>
  <atom:content type="html">get various OS statistics about a filefile_stat returns various information for an OS file by calling stat () system call and converting the relevant value to a varchar. The path is relative to the server&#39;s working directory. The what is an integer value selecting what information to return. If you don&#39;t supply second argument to the function it defaults to mode = 0. The DirsAllowed and DirsDenied lists in Parameters section of the virtuoso configuration file (virtuoso.ini by default) are not used to control disk access.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_to_string.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_to_string.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_to_string</atom:title>
  <atom:content type="html">returns the contents of a file as a varcharThis function requires dba privileges. Returns the contents of a file as a varchar value. The file&#39;s length is limited to 16 MB. The path is relative to the working directory of the database server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_to_string_output.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_to_string_output.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_to_string_output</atom:title>
  <atom:content type="html">get contents of a file as a string output streamThis function requires dba privileges. This function returns a string output stream initialized to contain the text of the file or its segment, on local file system path relative to the server&#39;s working directory. file_to_string_output can handle longer files than file_to_string and the resulting string output, if too long to be converted into a varchar, can be stored inside a blob.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_file_unlink.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_file_unlink.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: file_unlink</atom:title>
  <atom:content type="html">Delete a file from the file systemThis function requires dba privileges. This function deletes a file from the file system. sys_unlink is a synonym of this function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_fk_check_input_values.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_fk_check_input_values.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: fk_check_input_values</atom:title>
  <atom:content type="html">alter default foreign key checking behavior Enforcing foreign key constraints is enabled by default. This function allows globally disabling it without however disabling all triggers. This may be useful for large data imports or other special circumstances. The return value is the previous state of this setting, 0 for off, 1, for on. The effect of this function is persistent and survives server restart.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_floor.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_floor.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: floor</atom:title>
  <atom:content type="html">Round a number to negative infinity.floor calculates the largest integer smaller than or equal to x.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ftp_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ftp_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ftp_get</atom:title>
  <atom:content type="html">FTP get command; Virtuoso FTP clientVirtuoso has FTP client functionality, that can be used inside Virtuoso/PL. This Virtuoso function mimics the FTP get command. As with any PL, this can be combined with Web Services and SOAP.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ftp_ls.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ftp_ls.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ftp_ls</atom:title>
  <atom:content type="html">FTP dir command; Virtuoso FTP clientVirtuoso has FTP client functionality, that can be used inside Virtuoso/PL. This Virtuoso function mimics the FTP dir command. As with any PL, this can be combined with Web Services and SOAP.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ftp_put.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ftp_put.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ftp_put</atom:title>
  <atom:content type="html">FTP put command; Virtuoso FTP clientVirtuoso has FTP client functionality, that can be used inside Virtuoso/PL. This Virtuoso function mimics the FTP put command. As with any PL, this can be combined with Web Services and SOAP.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_gz_file_open.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_gz_file_open.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: gz_file_open</atom:title>
  <atom:content type="html">returns the contents of a gzipped fileReturns the contents of a file. The path is relative to the working directory of the database server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_get_certificate_info.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_get_certificate_info.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: get_certificate_info</atom:title>
  <atom:content type="html">Returns information about the current client X509 certificate This function will return information about the current client X509 certificate (if successfully verified). If there is no valid X509 certificate or the requested information is not available it will return NULL. If the optional cert_or_key_name is supplied it should contain a encoded certificate (by default format is PEM). The certificate info is read from the first certificate in that string. If the optional cert_or_key_name is supplied and in_format is equal to 3 (integer) the function will try to retrieve the certificate registered in the current user&#39;s key store by name contained in cert_or_key_name.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_get_keyword.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_get_keyword.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: get_keyword</atom:title>
  <atom:content type="html">Find a value in keyword vectorget_keyword performs a case sensitive seek for the occurrence of keyword from each even position of searched_array. If found,this returns the element following the occurrence of the keyword. If the keyword is not found this returns the default argument or NULL if the default is not supplied.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_get_keyword_ucase.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_get_keyword_ucase.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: get_keyword_ucase</atom:title>
  <atom:content type="html">Find a value in keyword vector (search uppercase)Identical to get_keyword except all comparisons are performed case insensitively.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_get_timestamp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_get_timestamp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: get_timestamp</atom:title>
  <atom:content type="html">returns the timestamp of the current transactionget_timestamp is merely an alias for now and is provided for backward compatibility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_getdate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_getdate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: getdate</atom:title>
  <atom:content type="html">returns the current transaction timestamp, alias of nowgetdate() returns the timestamp associated with current transaction. This is an alias of now().</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_gz_compress.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Compression<atom:link href="http://docs.openlinksw.com/virtuoso/fn_gz_compress.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: gz_compress</atom:title>
  <atom:content type="html">Compress data using gzip algorithm The gz_compress returns its argument compressed with the gzip algorithm. The argument and return values are arbitrary strings, possibly including any 8 bit characters.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_gz_uncompress.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Compression<atom:link href="http://docs.openlinksw.com/virtuoso/fn_gz_uncompress.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: gz_uncompress</atom:title>
  <atom:content type="html">Uncompress a string using gzip algorithmgz_uncompress takes a string argument, uncompresses it using the gzip algorithm, writing it to a string_output given as the second argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_hour.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_hour.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: hour</atom:title>
  <atom:content type="html">get hour from a datetimehour takes a datetime and returns an integer containing a number representing the hour of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http</atom:title>
  <atom:content type="html">write to HTTP client or a string output streamhttp writes val_expr to HTTP client or, if parameter stream is given, to the given string output stream. val_expr may be any scalar object, i.e. string, date or number and will automatically be cast to varchar before further processing. http will print out the string without escapes. http_value uses HTML escapes and http_url URL escapes.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_acl_set.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_acl_set.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_acl_set</atom:title>
  <atom:content type="html">Set conditions against web server ACL&#39;sThis function can be used within application logic to set ACLs rule.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_acl_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_acl_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_acl_get</atom:title>
  <atom:content type="html">Test conditions against web server ACL&#39;sThis function can be used within application logic to test that an internet client would not violate the ACL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_acl_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_acl_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_acl_remove</atom:title>
  <atom:content type="html">Removes conditions against web server ACL&#39;sThis function can be used within application logic to remove ACLs rule.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_body_read.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_body_read.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_body_read</atom:title>
  <atom:content type="html">Reads the HTTP body from the client HTTP connection and returns it as a string. This function reads the HTTP body from the client HTTP connection and returns it as a string output. This is suitable for processing POST requests with bodies encoded differently than multipart/* and application/x-www-form-urlencoded as in SOAP requests where the POST body is encoded as text/xml).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_client.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_client.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_client</atom:title>
  <atom:content type="html">returns a varchar containing the body of the request uriThis function is used to perform HTTP operations to retrieve generic content and/or to perform generic operations over HTTP/HTTPS protocols. It also supports HTTP authentication based on username/password credentials. If the URL is https: an no x509 certificate given then it will operate as https client w/o client certificate.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_client_ext.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_client_ext.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_client_ext</atom:title>
  <atom:content type="html">returns a varchar containing the body of the request uriThis function is used to perform HTTP operations to retrieve generic content and/or to perform generic operations over HTTP/HTTPS protocols. It also supports HTTP authentication based on username/password credentials. If the URL is https: an no x509 certificate given then it will operate as https client w/o client certificate.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_client_ip.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_client_ip.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_client_ip</atom:title>
  <atom:content type="html">Returns the IP address of the calling client.This function is used to determine the IP address or DNS name of the calling client. Please note that this function is slow when resolving a DNS names. It is advisable to use IP addresses to to make applications faster.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_debug_log.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_debug_log.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_debug_log</atom:title>
  <atom:content type="html">set WebDAV HTTP request loggingWhen an valid path string is supplied and it is allowed in file ACL list, the WebDAV HTTP requests and responses will be logged in append mode in to that file. When an open logging session is encountered the second call will produce an error. Specifying a NULL instead of file_path string stops the logging. The log file consists of lines with following fields:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_enable_gz.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_enable_gz.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_enable_gz</atom:title>
  <atom:content type="html">Enable / Disable &quot;Content-Encoding: gzip&quot; for HTTP server Enable (1)/ Disable (0) &quot;Content-Encoding: gzip&quot; for HTTP server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_file.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_file.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_file</atom:title>
  <atom:content type="html">Send a file to the HTTP client This function causes the contents of the file specified by path to be sent as the response of the calling request. The file is not sent until the code calling this returns. Content types etc. are defaulted based on the file&#39;s extension. If this function is called, other output to the HTTP client by the caller is discarded.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_flush.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_flush.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_flush</atom:title>
  <atom:content type="html">Flush internal HTTP stream and disconnect client; Flush HTTP stream and try sending data in chunked mode. This flushes the internal buffer where output of a VSP page is stored pending the execution of the page&#39;s code. This sends the content of the page output buffer along with headers and disconnects the client. The status is 200 OK by default, unless overridden by http_status. The purpose of this function is to allow a page to send output before terminating , thus the page can continue processing for an indefinite time without requiring the client to wait. This is useful for starting long running background tasks from HTTP clients. VSP pages that use this function must be sure to supply appropriate content (or response headers) if needed before calling this function. Virtuoso supports HTTP 1.1 Chunking Encoding which allows Virtuoso to send the user agent chunks of output as the page is still processing. Chunking is enabled by calling http_flush(1) within the VSP page. By default chunks are sent for every 4k worth of output generated, but in some cases the output needs to consist of smaller chunks, for example when run-time status needs to be shown in a status page. So to achieve this the http_flush (try_what=1) could be invoked in places where chunk must be flushed to the User agent.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_get</atom:title>
  <atom:content type="html">returns a varchar containing the body of the request urihttp_get returns a varchar containing the body of the requested target_uri or NULL if the body is not received.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_header.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_header.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_header</atom:title>
  <atom:content type="html">Specifies non-default HTTP response headers This function is used to add additional HTTP header lines to the server response. The http_header parameter MUST finish with &lt;CR&gt;&lt;LF&gt; characters. Warning: Each call of this function cancels the effect of the previous call. In order to add to previously set header lines, use the http_header_get function to retrieve the current headers. A Content-Type or Media-Type header specified as a part of the headers given with this function will override the default. Otherwise the header lines set using this function add to but do not replace the default response headers. Note that this function cannot set the status line. Use http_request_status for that.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_header_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_header_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_header_get</atom:title>
  <atom:content type="html">returns header of current HTTP request Returns the response header associated with the current HTTP request. This will not return the default header lines, only those explicitly set with http_header. This is useful for incrementally modifying response headers during processing of a URL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_kill.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_kill.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_kill</atom:title>
  <atom:content type="html">Kill VSP process whose details match parameter inputsThis function requires dba privileges. This function is used to kill the process whose details match that of the input parameters. If Client&#39;s IP and URL are specified, then it will try to kill all matching pending HTTP requests for that peer requesting that URL. If all three parameters are given, then it will try to kill only that pending HTTP request.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_listen_host.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_listen_host.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_listen_host</atom:title>
  <atom:content type="html">Starts, stops and retrieves the state of a user-defined HTTP listenerThis function requires dba privileges. This function is used to start, stop or lookup the state of user-defined HTTP and HTTPS listeners. The return value is 0 or 1 and indicates state of the listener, 1 for started and 0 for stopped.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_map_table.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_map_table.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_map_table</atom:title>
  <atom:content type="html">Update internal HTTP mapping tableThis function requires dba privileges. This function inserts an entry defining a virtual directory into the HTTP maps table.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_map_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_map_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_map_get</atom:title>
  <atom:content type="html">get values from HTTP virtual host path mapping table Retrieves information associated with the virtual host / HTTP path mapping in effect for the VSP page being processed. Values valid in current connection or URL context may be retrieved by element_name. Calling http_map_get has no use outside of http context. In this case an error will be signalled.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_param.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_param.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_param</atom:title>
  <atom:content type="html">returns value of a HTML form parameter in VSP contextThis function is used to return value of a HTML form parameter in VSP context. It&#39;s almost like call get_keyword (&#39;name&#39;, params) used in VSP programming. When &#39;name&#39; parameter is not supplied, the result of http_param() call will be all parameters, as they are contained in &#39;params&#39; parameter of the VSP pages. This function is useful in HTTP authentication PL hook, as in this place there is no &#39;params&#39; argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_path.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_path.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_path</atom:title>
  <atom:content type="html">returns the absolute path to the logical path location of the current http request This function returns the absolute path to the logical path location of current HTTP request.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_pending_req.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_pending_req.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_pending_req</atom:title>
  <atom:content type="html">return array describing running VSP threadsThis function requires dba privileges. http_pending_req returns an array of arrays of data on running VSP requests. Each array contains the Client IP Address, URL, and Process Request ID. These values can be used with the http_kill() function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_physical_path.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_physical_path.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_physical_path</atom:title>
  <atom:content type="html">returns the physical path location of the requested URL This function returns the absolute path to the physical path location of current HTTP request</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_proxy.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_proxy.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_proxy</atom:title>
  <atom:content type="html">proxy request to another host and return content to calling client This function is used to retrieve content from a foreign host and send the response to the HTTP client of the page calling this. This is useful for re-routing a request to another server in the middle of a VSP page.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_request_header.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_request_header.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_request_header</atom:title>
  <atom:content type="html">returns array of HTTP request header lines This function provides access to the HTTP request header lines.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_request_status.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_request_status.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_request_status</atom:title>
  <atom:content type="html">set the status sent to the client in an HTTP response This allows a VSP page to control the status sent to the client in the HTTP response. The argument will be presented as the first line of the reply instead of the default &quot;HTTP/1.1 200 OK&quot;. The string should not contain a CR or LF at the end. This allows a page to issue redirects, authentication challenges etc. Use it with http_headers to control the content of the HTTP reply headers.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_request_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_request_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_request_get</atom:title>
  <atom:content type="html">Access to the HTTP request line This function is used to access the HTTP request line within VSP or VSPX context. It returns &#39;CGI&#39; style variables for protocol version, HTTP method and query string.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_rewrite.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_rewrite.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_rewrite</atom:title>
  <atom:content type="html">Clears output written to a string output or to an HTTP This clears any previous output to the stream. If the stream is omitted or 0 the stream is the HTTP client stream of the calling procedure. All output from VSP page procedures is buffered into a local string stream before being sent out. This is done so as to support the HTTP/1.1 required content length and to allow recovery from errors.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_root.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_root.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_root</atom:title>
  <atom:content type="html">Returns the absolute path of the server root directory.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_value.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_value.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_value</atom:title>
  <atom:content type="html">write to HTTP client or string output stream with HTML escapesThe http_value is used to write to an HTTP client (when in a VSP context) or a specified string output stream. http_value uses HTML-escapes for characters that should be escaped according to the HTML spec.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_url.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_url.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_url</atom:title>
  <atom:content type="html">write to HTTP client or string output stream with URL escapesThe http_url is used to write to an HTTP client (when in a VSP context) or a specified string output stream. http_url uses URL escapes for special characters.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_http_xslt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_http_xslt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: http_xslt</atom:title>
  <atom:content type="html">applies an XSLT stylesheet to the output of a VSP page This function can be called inside a VSP page to apply an XSLT stylesheet to the output of the page once the page is complete. This function will return immediately and the stylesheet will not be applied until the page is successfully formed. Any errors arising in the stylesheet processing will be reported to the web client. The stylesheet does not have to be previously defined. The URI supplied will be used to locate the stylesheet. This can be a file, an HTTP URL or a virt:// URI for a stylesheet stored in a local table. Virtuoso will cache the stylesheet after first use. You can clear the cache entry with the xslt_stale() function. For this to work the text generated by the VSP page should be well-formed XML.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_urlrewrite_create_regex_rule.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_urlrewrite_create_regex_rule.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: URLREWRITE_CREATE_REGEX_RULE</atom:title>
  <atom:content type="html">Creates regex rules.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_identity_value.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_identity_value.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: identity_value</atom:title>
  <atom:content type="html">returns the last assigned identity column valueThis function returns the value assigned to an identity column by the previous insert statement. Insert statements that do not assign identity columns do not affect this. Note that tables that have no primary key have n invisible identity column called _IDN. The scope is the connection. This function may be called from a client or from a stored procedure and will return the last given identity column value wherever it was given. The value stays set until overwritten by the next insert operation. This value is not set by rexecute or inserts to remote tables with autoincrement columns declared on the remote database since there is no standard way of getting this information from remote data sources. The same value can be more efficiently accessed from clients using the SQLGetStmtOption ODBC call with the option SQL_GETLASTSERIAL. In this case the value is of type SQLINTEGER.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_import_clr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>User Defined Types &amp; The CLR<atom:link href="http://docs.openlinksw.com/virtuoso/fn_import_clr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: import_clr</atom:title>
  <atom:content type="html">This function automatically creates the SQL Type wrappers based on the CLR Reflection API.This function automatically creates the SQL Type wrappers based on the CLR Reflection API.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_import_jar.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_import_jar.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: import_jar</atom:title>
  <atom:content type="html">Creates SQL wrapper types of selected Java classesThis function calls the jvm_ref_import() function to produce the XML, then transforms it to a set of CREATE TYPE statements and executes them. The SQL names of the types are generated by retrieving the fully qualified name of the Java class and substituting the . with _ (e.g.: java.lang.System becomes java_lang_System). The names of the static members observer functions are composed by prepending the name of the static member with &#39;get&#39; so the static Java member stat_m is mapped to a SQL static method getstat_m(). As a result it creates SQL type wrappers for the specified Java classes.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_initcap.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_initcap.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: initcap</atom:title>
  <atom:content type="html">returns its argument with the first letter capitalizedinitcap returns a copy of string str with the first character, if it is a lowercase letter, converted to the corresponding uppercase letter. Otherwise, an identical copy of the string is returned. Notes about ucase apply also here.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_internal_to_sql_type.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_internal_to_sql_type.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: internal_to_sql_type</atom:title>
  <atom:content type="html">returns the integer standard SQL type of its argumentinternal_to_sql_type returns an integer value representing the standard SQL type converted from internal_type given as its argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_internal_type.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_internal_type.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: internal_type</atom:title>
  <atom:content type="html">returns internal integer datatype of its argumentinternal_type returns an integer value representing the internal type of its argument. These values are the same as what Virtuoso uses in the column COL_DTP of the system table SYS_COLS for keeping the track of the default types of each column of each table.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_internal_type_name.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_internal_type_name.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: internal_type_name</atom:title>
  <atom:content type="html">returns the internal type name of the argumentinternal_type_name returns a string which is a human-readable name for an internal_type integer given as its argument. The function dv_type_title() is an alias of internal_type_name().</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isarray.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isarray.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isarray</atom:title>
  <atom:content type="html">Check for a valid arrayisarray is true if the argument is a valid argument to aref. This is the case for any string or vector.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isblob.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isblob.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isblob</atom:title>
  <atom:content type="html">returns true if its argument is of type long varcharisblob returns one if its argument as a handle to an object of the type LONG VARCHAR, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isbinary.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isbinary.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isbinary</atom:title>
  <atom:content type="html">returns true if its argument is of type varbinaryisbinary returns one if its argument is of type VARBINARY, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isdouble.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isdouble.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isdouble</atom:title>
  <atom:content type="html">returns true is argument is a double isdouble returns one if its argument is of type double precision float, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isentity.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isentity.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isentity</atom:title>
  <atom:content type="html">returns true if its argument is an XML entityisentity is true if the argument is an XML entity object, such as that returned from XPATH expressions etc.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isfloat.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isfloat.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isfloat</atom:title>
  <atom:content type="html">returns true if its argument is a floatisfloat returns one if its argument is of type single float, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isinteger.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isinteger.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isinteger</atom:title>
  <atom:content type="html">returns true if its argument is of type integerisinteger returns one if its argument is of type integer, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isnull.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isnull.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isnull</atom:title>
  <atom:content type="html">returns true if its argument is NULLisnull returns one if its argument is NULL, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isnumeric.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isnumeric.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isnumeric</atom:title>
  <atom:content type="html">returns true if argument is of numeric typeisnumeric returns one if its argument is of type integer, single float or double precision floating point number, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_isstring.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_isstring.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: isstring</atom:title>
  <atom:content type="html">returns true if its argument is of type varcharisstring returns one if its argument is of type VARCHAR, zero otherwise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_iszero.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_iszero.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: iszero</atom:title>
  <atom:content type="html">returns true if argument is numeric zero iszero returns one if its argument is an integer 0, a float 0.0 or a double 0.0 For any other arguments, of whatever type, it will return zero.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_java_call_method.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Java PL API<atom:link href="http://docs.openlinksw.com/virtuoso/fn_java_call_method.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: java_call_method</atom:title>
  <atom:content type="html">Calls a class method using the supplied parameters (if any) and returns the return value (if any). If instance_obj is supplied (not NULL) then this function searches for a non-static method otherwise for static.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_java_set_property.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Java PL API<atom:link href="http://docs.openlinksw.com/virtuoso/fn_java_set_property.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: java_set_property</atom:title>
  <atom:content type="html">Sets a Java class propertyAssigns a new value to either a Java class instance property referenced by instance_obj, or if instance_obj is not supplied (NULL) then sets a static Java class property.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_java_get_property.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Java PL API<atom:link href="http://docs.openlinksw.com/virtuoso/fn_java_get_property.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: java_get_property</atom:title>
  <atom:content type="html">Gets a property value from a Java class instance.Gets a property value from a Java class instance referenced by instance_obj. If instance_obj is not supplied, ie NULL, then it is returned as a static Java class property value.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_java_load_class.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Java PL API<atom:link href="http://docs.openlinksw.com/virtuoso/fn_java_load_class.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: java_load_class</atom:title>
  <atom:content type="html">Declares a Java class to a Java VMDefines a java class into the running Java VM. This is useful for loading .class/.jar/.zip files from a BLOB column or from the Virtuoso WebDAV repository.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_java_new_object.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Java PL API<atom:link href="http://docs.openlinksw.com/virtuoso/fn_java_new_object.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: java_new_object</atom:title>
  <atom:content type="html">Creates and instance of a Java class.Creates an instance of a java class, makes a global reference in the Java VM and returns it to Virtuoso as a PL object reference value.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_java_vm_attach.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Java PL API<atom:link href="http://docs.openlinksw.com/virtuoso/fn_java_vm_attach.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: java_vm_attach</atom:title>
  <atom:content type="html">Ensures that the current working thread is attached to the Java VM. It operates as follows: The java_vm_attach() function is called implicitly in each of the other VSEs, and also when allocating, copying or deleting a Virtuoso/PL reference to a Java VM object values. If the Java VM is already initialized and the classpath is supplied it will throw a SQL error. If the Java VM is not initialized, but it is required to execute a statement the server will implicitly call java_vm_attach (NULL);. The Virtuoso Java VM integration binary works with JDK 1.2 and later.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_java_vm_detach.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtuoso Java PL API<atom:link href="http://docs.openlinksw.com/virtuoso/fn_java_vm_detach.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: java_vm_detach</atom:title>
  <atom:content type="html">Detaches the current Virtuoso working thread from the Java VM.Detaches the current Virtuoso working thread from the Java VM.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_jvm_ref_import.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_jvm_ref_import.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: jvm_ref_import</atom:title>
  <atom:content type="html">Creates XML description of Java classThis function will returns an XML description of the selected classes from the source files. The XML produced by the JVM_REF_IMPORT can be supplied to the predefined XSL style sheet __javavm_type to produce the CREATE TYPE statements: This can also be achieve directly using a single call to:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_lcase.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_lcase.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: lcase</atom:title>
  <atom:content type="html">Converts string argument to lower caselcase returns a copy of string str with all the uppercase alphabetical characters converted to corresponding lowercase letters. This includes also the diacritic letters present in the ISO 8859/1 standard in range 192 - 222 decimal, excluding the character 223, German double-s which stays the same. lower is an alias for lcase.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ldap_search.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>LDAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ldap_search.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ldap_search</atom:title>
  <atom:content type="html">Search in an LDAP server. This function performs a search in the LDAP server. It returns control to the Virtuoso/PL environment only after all of the search results have been sent by the server or if the search request is timed out by the server. The result of the search (attributes, names of the attributes, etc.) will be returned as an array result. Options to the LDAP search can be passed as an array.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ldap_delete.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>LDAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ldap_delete.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ldap_delete</atom:title>
  <atom:content type="html">Remove a leaf entry in the LDAP Directory Information Tree. This function removes a leaf entry in the LDAP Directory Information Tree.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ldap_add.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>LDAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ldap_add.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ldap_add</atom:title>
  <atom:content type="html">Adds a new entry to an LDAP directory.This function adds a new entry to the LDAP directory.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ldap_modify.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>LDAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ldap_modify.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ldap_modify</atom:title>
  <atom:content type="html">Modifies an existing LDAP directory.This function modifies an existing LDAP directory entry.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_left.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_left.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: left</atom:title>
  <atom:content type="html">returns substring taken from left of string argumentleft returns a subsequence of string str, taking count characters from the beginning of the string. If count is zero an empty string &#39;&#39; is returned. If length of str is less than count then a copy of the whole str is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_length.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_length.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: length</atom:title>
  <atom:content type="html">Get length of argumentReturns the length of its argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_lfs_exp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_lfs_exp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: LFS_EXP</atom:title>
  <atom:content type="html">Export retrieved web site to the local file systemThis function is used to export local content retrieved from a Web Robot Copy to the local file system.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_lh_get_handler.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_lh_get_handler.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: lh_get_handler</atom:title>
  <atom:content type="html">Returns language handler</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_lh_load_handler.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Locale<atom:link href="http://docs.openlinksw.com/virtuoso/fn_lh_load_handler.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: lh_load_handler</atom:title>
  <atom:content type="html">Loads given handler in global table of the server Loads given handler in global table of the server, using ISO 639 and RFC 1766 language IDs of the handler as keys for future table lookups. If another handler was already specified for given RFC 1766 id, table entry will be updated and will refer to new handler. If another handler was already specified for given ISO 639 id, it will be replaced only if new handler has ISO 639 language ID equal to its RFC 1766 ID. Please do not load custom versions of &#39;x-any&#39; and &#39;x-ftq-x-any&#39; handlers.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_locate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_locate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: locate</atom:title>
  <atom:content type="html">returns the starting position of the first occurrence of an substring in a string Returns the starting position of the first occurrence of string_exp1 within string_exp2. The search for the first occurrence of string_exp1 begins with the first character position in string_exp2 unless the optional argument, start, is specified. If start is specified, the search begins with the character position indicated by the value of start. The first character position in string_exp2 is indicated by the value 1. If string_exp1 is not found within string_exp2, the value 0 is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_log.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_log.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: log</atom:title>
  <atom:content type="html">calculate natural logarithm of an expressionlog calculates the natural logarithm of its argument and returns it as a IEEE 64-bit float.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_log10.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_log10.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: log10</atom:title>
  <atom:content type="html">Calculate 10-based logarithmslog10 calculates the 10-based logarithm of its argument and returns it as a IEEE 64-bit float.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_log_enable.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_log_enable.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: log_enable</atom:title>
  <atom:content type="html">controls transaction logging and in-statement autocommitThe log_enable function allows turning off or on regular transaction logging or autocommit after every changed row. The parameter bits is a bitmask. Two bits that are in use in current versions are 1 and 2. When bit 1 is not set (e.g. parameter value 0) then the function call terminates logging of DML statements inside the calling transaction. A value of 1 resumes logging of DML statements. If bit 2 is set then automatic commits take place after every change in every row in every DML statement. Thus a parameter value of 2 disables logging and enables row-by-row autocommit. A value of 3 enables row-by-row autocommit and enables logging. While log on and off setting alone is reset at the end of the transaction so that one does not end up with logging disabled by accident, the row-by-row autocommit mode causes the setting to be permanent inside the calling connection or web request. That is, for a SQL client the setting stays in effect until changed or disconnected and for a web request it stays in effect until the request is completed. The function do nothing if the bits is NULL. The function also do nothing when called inside atomic section. The function always returns the bitmask that describes old configuration of the log.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_log_text.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_log_text.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: log_text</atom:title>
  <atom:content type="html">inserts statements into the roll forward logThe log_text function can be used to insert a SQL statement into the roll forward log. The log_text function causes the SQL text given as first argument to be executed at roll forward time with the following arguments as parameters, bound from left to right to the parameter markers in the statement (&#39;?&#39;). There can be a maximum of 8 parameters but these can be arrays.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_lower.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_lower.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: lower</atom:title>
  <atom:content type="html">returns a lower case version of its argument lcase returns a copy of string str with all the uppercase alphabetical characters converted to corresponding lowercase letters. This includes also the diacritic letters present in the ISO 8859/1 standard in range 192 - 222 decimal, excluding the character 223, German double-s which stays the same. lower is just an alias for lcase.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ltrim.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ltrim.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ltrim</atom:title>
  <atom:content type="html">removes specific characters from a stringltrim returns a copy of subsequence of string str with all the characters present in trimchars trimmed off from the beginning. If the second argument is omitted, it is a space &#39; &#39; by default. rtrim is similar except that it trims from the right. trim trims from both ends.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_make_array.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_make_array.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: make_array</atom:title>
  <atom:content type="html">returns a new arrayThis returns an array of length elements with the content element type. The initial content of the array is undefined.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_make_string.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_make_string.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: make_string</atom:title>
  <atom:content type="html">make a stringmake_string returns a new string of length count, filled with binary zeros. If count is zero, an empty string &#39;&#39; is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_md5.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_md5.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: md5</atom:title>
  <atom:content type="html">returns the md5 checksum of its argumentmd5 calculates the MD5 checksum of its argument. The md5 message digest algorithm is defined in RFC1321.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_md5_init.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_md5_init.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: md5_init</atom:title>
  <atom:content type="html">returns the string serialization of a new md5 context This function initializes an MD5_CTX, converts it into varchar form and returns this representation. Should be used with md5_update/md5_final.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_md5_update.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_md5_update.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: md5_update</atom:title>
  <atom:content type="html">returns the updated md5 context serialized as varchar This function updates MD5_CTX with data parameter and returns the (deserialized from ctx parameter) updated context.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_md5_final.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_md5_final.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: md5_final</atom:title>
  <atom:content type="html">returns the md5 checksum given an initialized md5 contextThis function finalizes the MD5_CTX and returns the final checksum.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mime_body.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mime_body.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mime_body</atom:title>
  <atom:content type="html">used to compose multipart/mixed MIME message bodyThe mime_body() procedure is used to compose a multipart/mixed MIME body. it takes only one parameter, mime_parts, an array of mime_part elements such as those produced by the mime_part() function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mime_part.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mime_part.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mime_part</atom:title>
  <atom:content type="html">used to compose a MIME message body part.This function is used to make a MIME part that can be used with the mime_body() function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mime_tree.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mime_tree.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mime_tree</atom:title>
  <atom:content type="html">parses MIME messages into an array structure This function is intended to parse MIME (RFC2045) messages (coming from a RFC822 or HTTP sources). It parses the text and produces an array structure representing the structure of the MIME message. It copies into the structure MIME headers, but for the MIME bodies it only stores start and end offsets, thus optimizing space usage. The parameters to mime_tree are: If flag is 1, the &quot;root&quot; message follows RFC822. This means mime_tree will unfold the attributes, will scan for MIME registered header fields and will take their attributes. Alternately this can be a MIME message which needs no unfolding and has attributes separated with semicolon.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_minute.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_minute.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: minute</atom:title>
  <atom:content type="html">get minute from a datetimeminute takes a datetime and returns an integer containing a number representing the minute of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mod.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mod.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mod</atom:title>
  <atom:content type="html">returns the modulus of its argumentsmod returns the modulus (i.e. remainder) of the division dividend/divisor. If the divisor is zero the SQL error 22012 &quot;Division by zero&quot; is generated.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_month.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_month.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: month</atom:title>
  <atom:content type="html">get number of month from a datetimemonth takes a datetime and returns an integer containing a number representing the month of year of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_monthname.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_monthname.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: monthname</atom:title>
  <atom:content type="html">get name of month from a datetimemonthname takes a datetime and returns a string containing name of the month represented by the datetime</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_msec_time.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_msec_time.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: msec_time</atom:title>
  <atom:content type="html">Get number of milliseconds from system epochmsec_time returns the number of milliseconds since system epoch. It is useful for benchmarking purposes, timing operations, etc.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mts_connect.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Transaction<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mts_connect.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mts_connect</atom:title>
  <atom:content type="html">connects Virtuoso server to MS DTC. If reconnect flag is set to non-zero value then forces Virtuoso to connect even it have been connected already. Returns zero if succeeds. If MS DTC service is not available (W2K) or MTS is not running (NT4.0) signals error with code &quot;MX000&quot;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mts_get_timeout.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Transaction<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mts_get_timeout.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mts_get_timeout</atom:title>
  <atom:content type="html">returns timeout of distributed transaction in milliseconds.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mts_set_timeout.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Transaction<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mts_set_timeout.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mts_set_timeout</atom:title>
  <atom:content type="html">sets timeout of distributed transaction. sets distributed transactions timeout. &#39;timeout&#39; parameter indicates amount of timeout in milliseconds. If it equals -1 then default timeout of Virtuoso transaction is used (SQL_QUERY_TIMEOUT). This function must be called directly after &quot;SET MTS_2PC=1&quot;. The time countdown begins at moment of changing first branch.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_mts_status.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Transaction<atom:link href="http://docs.openlinksw.com/virtuoso/fn_mts_status.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: mts_status</atom:title>
  <atom:content type="html">checks status of current transaction or server. Checks status of subject. Subject can be either &#39;MTS&#39; or &#39;TRANSACTION&#39;. In the first case this checks if the server is connected to MTS. In the second case, checks if 2pc control is enabled for the current transaction. This function returns status string. For &#39;MTS&#39; it could be either &#39;connected&#39; or &#39;disconnected&#39;. For &#39;TRANSACTION&#39; - either &#39;2pc enabled&#39; or &#39;2pc disabled&#39;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_name_part.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_name_part.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: name_part</atom:title>
  <atom:content type="html">Returns portion of dotted name such as a fully qualified table name.The name_part() can be used to dissecting parts of a three part names (string where items are divided by dots &quot;.&quot;) such as table names or columns names. The table name &quot;DB&quot;.&quot;DBA&quot;.&quot;SYS_USERS&quot; contains three parts which can be extracted individually using this function providing the correct index from a 0 base: 0 would return &quot;DB&quot;, 1 would return &quot;DBA&quot;, 2 would return &quot;SYS_USERS&quot;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_nntp_auth_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_nntp_auth_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: nntp_auth_get</atom:title>
  <atom:content type="html">returns information about an NNTP server with authorizationThe nntp_auth_get() is used to retrieve messages from a server requiring authorization. See nntp_get for more information.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_nntp_auth_post.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_nntp_auth_post.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: nntp_auth_post</atom:title>
  <atom:content type="html">Post message to NNTP server with authorization Nntp_auth_post is used to post a message to the server require authorization.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_nntp_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_nntp_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: nntp_get</atom:title>
  <atom:content type="html">Returns information about an NNTP server. nntp_get() is used to retrieve messages from a server running the Network News Transfer Protocol (NNTP) as defined in RFC977. It returns an array whose structure depends on the command parameter, thus:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_nntp_post.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_nntp_post.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: nntp_post</atom:title>
  <atom:content type="html">Post message to NNTP server Nntp_post is used to post a message to the server running the Network News Transfer Protocol as defined in the rfc977.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_now.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_now.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: now</atom:title>
  <atom:content type="html">returns the current transaction timestamp Now returns the timestamp associated with current transaction as a DATETIME. This value is guaranteed to differ from the timestamp of any other transaction.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_os_chmod.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_os_chmod.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: os_chmod</atom:title>
  <atom:content type="html">changes the file access mode of a fileos_chmod set the file mode bits by calling the system function chmod() with the arguments supplied. Not all the host OSes support all the file modes. That&#39;s why the function will not throw an SQL error if the function fails. It will return DB NULL value when the function was called successfully and the error message as a string if it failed.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_os_chown.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>File Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_os_chown.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: os_chown</atom:title>
  <atom:content type="html">changes the owning group/user of a fileThis function requires dba privileges. os_chown set the owning user/group of an OS file by calling the system function chown() with the arguments supplied. Not all the host OSes support the concept of owner users and groups. That&#39;s why the function will not throw an SQL error if it fails.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_pem_certificates_to_array.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_pem_certificates_to_array.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: pem_certificates_to_array</atom:title>
  <atom:content type="html">converts a PEM file to an array of PEM stringsThis gets a PEM file with (possibly) many X509 certificates among others and constructs an array containing each X509 certificate as a separate PEM string. This can serve for splitting a PEM file containing multiple certificates (for example CA file) to single certificate entries so it can be examined with get_certificate_info function. Note that the array can contain NULL elements in places where in the PEM file there are blocks other than X509 PEM certificates.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_pldbg_stats.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_pldbg_stats.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: pldbg_stats</atom:title>
  <atom:content type="html">Makes an array of line/count information based on current coverage.This function is used to make an array of line/count information based on the current coverage statistics. If the procedure name is given (first param), then the result will contain only coverage statistic for that procedure. if the procedure name is not supplied or supplied as NULL then the result will contain coverage data for all procedures having statistic. The add_line_info flag is used to add code excerpt on line info.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_pldbg_stats_load.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_pldbg_stats_load.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: pldbg_stats_load</atom:title>
  <atom:content type="html">Used to load a coverage of a single procedure record as an array.This function is used to load coverage information for a single procedure record. The expected format is an array. The data expected is exactly that which can be produced by pldbg_stats(). Only one record will can be accepted, an array of several procedure records will not be acceptable.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_pop3_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_pop3_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: pop3_get</atom:title>
  <atom:content type="html">get messages from a POP3 serverPop3_get is used to retrieve and delete messages from a server running the Post Office Protocol version 3 as defined in rfc1725. In its default form it returns a vector of vectors containing messages retrieved from the POP3 server. Each vector within the vector contains a pair of VARCHAR UIDL and VARCHAR Message body, i.e. to get the message body of the second message retrieved, one would use aref (aref (msg_vec, 1), 1). Total length of messages retrieved will not exceed the value of buffer_size parameter in bytes. The optional parameter command can be used to control output or delete messages. When command is passed a VARCHAR &#39;uidl&#39;, pop3_get outputs single vector containing VARCHAR UIDLs. The buffer_size constraint is effective here. Thus, the vector will only contain UIDLs of messages whose total message text length does not exceed buffer_size bytes. These message lengths are accumulated in the order returned by the POP3 server. Command &#39;delete&#39; will cause retrieved messages to be deleted from the server after retrieval.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_position.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_position.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: position</atom:title>
  <atom:content type="html">returns the index of an element within an array or stringposition returns the one-based index for the first occurrence of element within an array or string, beginning from offset start_index and iterating with step. If the second argument is a string, the first argument must be a string with a single character. If the second argument is an array of any, then depending of type of it&#39;s elements same type is expected as the first argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_power.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_power.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: power</atom:title>
  <atom:content type="html">return value of expression raised to specified power.power raises x to the yth power and returns the value as a IEEE 64-bit float.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_prof_enable.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_prof_enable.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: prof_enable</atom:title>
  <atom:content type="html">Control virtuoso profilingprof_enable is used to enable or disable profiling of execution times, SQL statements and web requests. Passing flag value 1, enables profiling, causing times of statement executions, which begin and end while profiling is on, to be accumulated. When called with a flag of 0, the accumulation is stopped and results gathered so far are written into file named virtprof.out in the server&#39;s working directory. For a description of the file, see section about SQL Execution Profiling in Performance tuning part of Virtuoso documentation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_prof_sample.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_prof_sample.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: prof_sample</atom:title>
  <atom:content type="html">Adds a profiling sample to a profile being accumulated.prof_sample is used to adds a profiling sample to a profile being accumulated. The first argument is the name of the sampled section, the times called and cumulative times will be totaled under this heading. The second argument is the time in milliseconds. The third argument is a flag indicating whether the section was successfully executed. 0 indicates success, 1 indicates execute of the statement, 2 indicates fetch on a statement&#39;s resultset, 4 indicates error. For more description of profiling capabilities see the section about SQL Execution Profiling in Performance tuning part of Virtuoso documentation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_quarter.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_quarter.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: quarter</atom:title>
  <atom:content type="html">get number of quarter of year from a datetimequarter takes a datetime and returns an integer containing a number representing the quarter of year of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_quote_dotted.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_quote_dotted.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: quote_dotted</atom:title>
  <atom:content type="html">Returns an quoted identifier.The quote_dotted() function will return the identifier (table name or column name) appropriately quoted for the remote data source. This function will obtain the appropriate quote characters from the remote data source. This function can be used in conjunction with rexecute function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_randomize.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_randomize.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: randomize</atom:title>
  <atom:content type="html">initializes the random number generator The rnd function returns a random number between zero and n - 1, inclusive. randomize initializes the random number generator. The random number generator is initialized after the clock at first usage, so the produced sequences will be different each time unless specifically initialized.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rclose.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rclose.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rclose</atom:title>
  <atom:content type="html">Closes cursor created by rexecute()Closes the cursor opened to a remote DSN by the rexecute() function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regexp_match.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regexp_match.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: regexp_match</atom:title>
  <atom:content type="html">returns a substring matching the regular expression to the supplied string The regexp_match function returns a copy of substring of string str which matches the regular expression pattern. Previous behavior of this function would cut the first characters of str until the end of regular expression matched substring. In this way str could be passed to this function again to find the next occurrence of substring that matches the regular expression. By default this behavior is not adopted by this function, but can be enabled for pre 3.2 compatibility by supplying the optional third parameter. If either the pattern or str parameter contain wide characters this function will operate in wide mode, first converting any narrow characters to wide and returning a wide character response. Otherwise this function operates in narrow mode by default.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regexp_parse.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regexp_parse.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: regexp_parse</atom:title>
  <atom:content type="html">returns substrings that match the regular expression in supplied string after an offset It applies regular expression to target_str with offset. This function returns a vector containing 2 elements for first match of the pattern and if there a sub expressions : 2 elements for each of subexpression match. The first (even numbered) element of each pair is the start index and the second (odd numbered) is the end index of the match. The regexp_parse function is more efficient than regexp_match and regexp_substr, because it doesn&#39;t allocate strings. Where: 2-14 is a range matched by whole expression, 2-4 is a range where &#39;(2[34])&#39; is matched , and 12-14 is a range where &#39;(2[35])&#39; subexpression matched.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regexp_substr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regexp_substr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: regexp_substr</atom:title>
  <atom:content type="html">returns a single captured substring from matched substringThis function will return the whole string value of the first substring in &quot;str&quot; that matches the regexp in &quot;pattern&quot; or a sub part of the first match. The regexp syntax allows subexpressions to be marked in the regular expression (using the braces syntax). An example of such type of expression will be: &#39;(2[34]).*(2[35])&#39; which means a regular expression having two subexpressions: &#39;2[34]&#39; and &#39;2[35]&#39;. Let&#39;s apply the above regexp to the following source string: 22232225222323 This returns the hole matched string from the expression.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_audit_metadata.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_audit_metadata.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_AUDIT_METADATA</atom:title>
  <atom:content type="html">Fix RDF metadata corruption.This function can detect and automatically fix most popular sorts of metadata corruption.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_backup_metadata.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_backup_metadata.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_BACKUP_METADATA</atom:title>
  <atom:content type="html">Makes a backup copy of RDF metadata (i.e., descriptions of RDF Views and the like). This saves all RDF metadata to file or to some graph in RDF storage, depending on first argument (nonzero for file, zero for graph). If the function gets nonzero as first argument then it creates two files, called, say, &#39;example.ttl&#39;, and &#39;example-DEBUG.ttl&#39;. It&#39;s enough to save only the former file in order to restore metadata later, but the latter contains important additional debug information so both files should be attached to any bug report related to RDF metadata. There are no functions to make copies of backups. File backup consists of plain TURTLE RDF files only. Backup graph is just a regular RDF graph in the default storage so it can be serialized into a file or copied into other graph. However it is important to remember that the system graph, whose name is returned by JSO_SYS_GRAPH() stored procedure, should not be edited directly. The content of the system graph is not necessarily equal to the content of a backup graph and it should be touched only by API function calls.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_void_store.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_void_store.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_VOID_STORE</atom:title>
  <atom:content type="html">Collects statistics for a given graph and saves it.Collects statistics for the first given graph and saves the result into the second graph. For correct results, the first graph should be loaded in the database before executing the function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_restore_metadata.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_restore_metadata.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_RESTORE_METADATA</atom:title>
  <atom:content type="html">Restores RDF metadata (descriptions of RDF Views and the like) from previously saved backup.This restores RDF metadata from specified file or graph in RDF storage. The file or graph should be previously created by DB.DBA.RDF_BACKUP_METADATA(). It is usually safe to restore metadata from backup made by some previous version of Virtuoso server but it is good idea to call DB.DBA.RDF_AUDIT_METADATA() after such restore. When the procedure is executed on the server that continues to serve user requests during the maintenance then SPARQL query compiler may interrupt query compilations or create queries that will return incomplete result sets. These queries may be cached till the end of metadata update procedure but the cache is flushed when the update is complete, so possible errors will be transient. If even transient errors are not appropriate then do RDF metadata update with all precautions usual for changing database schema of an application.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_load_rdfxml_mt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_load_rdfxml_mt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_LOAD_RDFXML_MT</atom:title>
  <atom:content type="html">Parses the content of large RDF/XML text as a sequence of separate RDF triples.For loading large resources when transactional integrity is not important (loading of a single resource may take more than one transaction). The function may or may not leave a transaction log, depending on log_mode. Hence, after successful load, one may need to execute the checkpoint statement to make sure that a server restart does not wipe out the results.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_load_rdfxml.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_load_rdfxml.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_LOAD_RDFXML</atom:title>
  <atom:content type="html">Parses the content of RDF/XML text as a sequence of separate RDF triples.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ttlp.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ttlp.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.TTLP</atom:title>
  <atom:content type="html">parses TTL (TURTLE or N3 resource) and places its triples into DB.DBA.RDF_QUAD.Parses TTL (TURTLE or N3 resource) and places its triples into DB.DBA.RDF_QUAD.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ttlp_mt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ttlp_mt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.TTLP_MT</atom:title>
  <atom:content type="html">parses TTL (TURTLE or N3 resource) and places its triples into DB.DBA.RDF_QUAD on multiple threads.Loads the TTL (TURTLE or N3 resource) file on multiple threads, using parallel I/O and multiprocessing if available. The function commit partial transactions while it runs so the transaction log may contain part of loading. Moreover, the function may or may not leave a transaction log, depending on log_mode. Hence, after successful load, one may need to execute the checkpoint statement to make sure that a server restart does not wipe out the results.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ttlp_mt_local_file.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ttlp_mt_local_file.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.TTLP_MT_LOCAL_FILE</atom:title>
  <atom:content type="html">parses TTL (TURTLE or N3 resource) and places its triples into DB.DBA.RDF_QUAD on multiple threads.Loads the TTL (TURTLE or N3 resource) file on multiple threads, using parallel I/O and multiprocessing if available. The function commit partial transactions while it runs so the transaction log may contain part of loading. Moreover, the function may or may not leave a transaction log, depending on log_mode. Hence, after successful load, one may need to execute the checkpoint statement to make sure that a server restart does not wipe out the results.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_triples_to_rdf_xml_text.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_triples_to_rdf_xml_text.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_TRIPLES_TO_RDF_XML_TEXT</atom:title>
  <atom:content type="html">Serializes vector of triples into a session, in RDF/XML syntax.Serializes vector of triples into a session, in TURTLE syntax. In current version, every triple is printed in separate top-level record (say, in rdf:Description tag), without any pretty-print or nesting optimization.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_triples_to_ttl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_triples_to_ttl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_TRIPLES_TO_TTL</atom:title>
  <atom:content type="html">Serializes vector of triples into a session, in TURTLE syntax.Serializes vector of triples into a session, in TURTLE syntax. In current version, every triple is printed in separate top-level record (say, in rdf:Description tag), without any pretty-print or nesting optimization.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_64bit_upgrade.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_64bit_upgrade.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_64BIT_UPGRADE</atom:title>
  <atom:content type="html">Alters IRI_ID columns to get IRI_ID_8.There are two data types. IRI_ID is 4-byte and IRI_ID_8 is 8-byte. Initially, IRI_ID columns are created. DB.DBA.RDF_64BIT_UPGRADE() alters them to get IRI_ID_8. Note that this is to hold more that 4G of distinct IRIs, number of distinct quads is not limited by 4G even without the upgrade. The function should be called once.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_convert_rdfxml_to_ttl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_convert_rdfxml_to_ttl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_CONVERT_RDFXML_TO_TTL</atom:title>
  <atom:content type="html">Converts rdf xml to ttl.Converts rdf xml to ttl.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdfs_rule_set.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdfs_rule_set.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rdfs_rule_set</atom:title>
  <atom:content type="html">Adds the applicable facts of the graph into a rule set.This function specifies a logical name for the rule set plus a graph URI. It is possible to combine multiple schema graphs into a single rule set. A single schema graph may also independently participate in multiple rule sets.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ann_phrase_class_add.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Phrases<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ann_phrase_class_add.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.ANN_PHRASE_CLASS_ADD</atom:title>
  <atom:content type="html">Returns APC_ID of a phrase class.The returned value is APC_ID of a class if positive or an error code if negative. To update phrase class, no special DB.DBA.ANN_PHRASE_CLASS_UPDATE() exists, use DB.DBA.ANN_PHRASE_CLASS_ADD() with parameter &quot;mode&quot; equal to &#39;replacing&#39;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ann_phrase_class_del.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Phrases<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ann_phrase_class_del.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.ANN_PHRASE_CLASS_DEL</atom:title>
  <atom:content type="html">Deletes phrase set.The returned value is APS_ID of a deleted phrase set if positive or an error code if negative. A phrase set can not be deleted while used by some advertiser (as described here).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ap_build_match_list.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Phrases<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ap_build_match_list.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: AP_BUILD_MATCH_LIST</atom:title>
  <atom:content type="html">Returns report of all occurrences of phrases from the specified sets in the text.Forms a report that lists all occurrences of phrases from the specified sets in the text. The report describes &quot;phrase hits&quot;, i.e. occurrences of annotation phrases in the text, using &quot;arrows&quot; that point to specific fragments in the text, such as words of found phrases or HTML tags. The structure of the report is complicated, due to contradiction in requirements. It is compact to provide reasonable performance and scalability, so common data should not be repeated, saving memory. It is complete enough to prevent application from reading omitted data from system tables, saving time.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ap_add_phrases.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Phrases<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ap_add_phrases.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: AP_ADD_PHRASES</atom:title>
  <atom:content type="html">Adds phrases to given set.The function gets two arguments, the integer ID of annotation phrase set and a vector of $ descriptions of phrases that should be edited in that phrase set. Every item of vector of descriptions is in turn vector of one or two values; first value is the text of the phrase, second value is associated application specific data, the absence of second value indicates that the phrase should be removed. If same text of phrase appears in the vector of description more than once, and associated data differ then any version of data can be stored for future use; it is the roll of dice because the vector is reordered for faster processing.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_iri_split.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_iri_split.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: iri_split</atom:title>
  <atom:content type="html">Splits into the namespace prefix and the local part according to the TTL rules.Iri is a qualified name. It is split into the namespace prefix and the local part according to the TTL rules. The prefix is returned. If a second argument is given, it is set to the local part.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn___xml_get_ns_prefix.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn___xml_get_ns_prefix.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: __xml_get_ns_prefix</atom:title>
  <atom:content type="html">Returns prefix by given URI.If str is a globally known namespace URI, its prefix is returned, else null. Flags is a bit mask where 1 means to look in the connection, 2 in the global set of known prefixes.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn___xml_get_ns_uri.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn___xml_get_ns_uri.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: __xml_get_ns_uri</atom:title>
  <atom:content type="html">Returns URI by given namespace prefix.If str is a globally known namespace prefix, its URI is returned, else null. Flags is a bit mask where 1 means to look in the connection, 2 in the global set of known prefixes.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sparql_eval.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sparql_eval.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.SPARQL_EVAL</atom:title>
  <atom:content type="html">Local execution of SPARQL via SPARQL protocol, produces a result set of SQL values.Local execution of SPARQL via SPARQL protocol, produces a result set of SQL values.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sparql_eval_to_array.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sparql_eval_to_array.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.SPARQL_EVAL_TO_ARRAY</atom:title>
  <atom:content type="html">Local execution of SPARQL via SPARQL protocol, produces a vector of vectors of SQL values.Local execution of SPARQL via SPARQL protocol, produces a result set of SQL values.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sparql_rexec.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sparql_rexec.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.SPARQL_REXEC</atom:title>
  <atom:content type="html">Remote execution of SPARQL via SPARQL protocol, produces a result set of SQL values.Remote execution of SPARQL via SPARQL protocol, produces a result set of SQL values.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sparql_rexec_to_array.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sparql_rexec_to_array.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.SPARQL_REXEC_TO_ARRAY</atom:title>
  <atom:content type="html">Remote execution of SPARQL via SPARQL protocol, produces a vector of vectors of SQL value.Remote execution of SPARQL via SPARQL protocol, produces a vector of vectors of SQL value.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sparql_rexec_with_meta.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sparql_rexec_with_meta.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.SPARQL_REXEC_WITH_META</atom:title>
  <atom:content type="html">Remote execution of SPARQL via SPARQL protocol. Fills in output parameters with metadata (like exec metadata) and a vector of vector s of &#39;long valmode&#39; values.Remote execution of SPARQL via SPARQL protocol. Fills in output parameters with metadata (like exec metadata) and a vector of vector s of &#39;long valmode&#39; values.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_regex.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_regex.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_REGEX</atom:title>
  <atom:content type="html">Returns 1 if string s matches pattern p, 0 otherwise.Returns 1 if string s matches pattern p, 0 otherwise</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_langmatches.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_langmatches.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_LANGMATCHES</atom:title>
  <atom:content type="html">Returns 1 if language identifier r matches lang pattern t.Returns 1 if language identifier r matches lang pattern t</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_ttl2hash.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_ttl2hash.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_TTL2HASH</atom:title>
  <atom:content type="html">Returns a dict of triples in &#39;long valmode&#39;.Returns a dict of triples in &#39;long valmode&#39;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_quad_uri.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_quad_uri.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_QUAD_URI</atom:title>
  <atom:content type="html">Performs simple insertion of a quad where object is a node.Performs simple insertion of a quad where object is a node. The arguments g_uri, s_uri and p_uri should be IRI strings or IRI_IDs. All string arguments should be in UTF-8 encoding, otherwise they will be stored but are not queryable via SPARQL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_quad_uri_l.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_quad_uri_l.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_QUAD_URI_L</atom:title>
  <atom:content type="html">Performs simple insertion of a quad where object is a literal value in &#39;SQL valmode&#39;.Performs simple insertion of a quad where object is a literal value in &#39;SQL valmode&#39;. The arguments g_uri, s_uri and p_uri should be IRI strings or IRI_IDs. All string arguments should be in UTF-8 encoding, otherwise they will be stored but are not queryable via SPARQL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rdf_quad_uri_l_typed.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>RDF data<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rdf_quad_uri_l_typed.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: DB.DBA.RDF_QUAD_URI_L_TYPED</atom:title>
  <atom:content type="html">Performs simple insertion of a quad where object is a literal value in &#39;SQL valmode&#39; and can be specified datatype and language.Performs simple insertion of a quad where object is a literal value in &#39;SQL valmode&#39; and can be specified datatype and language. The arguments g_uri, s_uri and p_uri should be IRI strings or IRI_IDs. All string arguments should be in UTF-8 encoding, otherwise they will be stored but are not queryable via SPARQL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regexp_replace.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regexp_replace.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: regexp_replace</atom:title>
  <atom:content type="html">Replaces occurrence(s) of the matching pattern in the source_string with a specified replace_string.This function replaces occurrence(s) of the matching pattern in the source_string with a specified replace_string, allowing complex search-and-replace operations. The traditional REPLACE SQL function substitutes one string with another. Assume your data has extraneous spaces in the text and you would like to replace them with a single space. With the REPLACE function, you would need to list exactly how many spaces you want to replace. However, the number of extra spaces may not be the same everywhere in the text.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regexp_instr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regexp_instr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: regexp_instr</atom:title>
  <atom:content type="html">Returns the first position of the occurrence of a regular-expression pattern in a given string.This function looks for a pattern and returns the first position of the pattern. Optionally, you can indicate the start_position you want to begin the search. The occurrence parameter defaults to 1 unless you indicate that you are looking for a subsequent occurrence. The default value of the return_option is 0, which returns the starting position of the pattern; a value of 1 returns the starting position of the next character following the match. This function returns the starting position of a pattern, so it works much like the familiar INSTR function. The main difference between the two functions is that REGEXP_INSTR lets you specify a pattern instead of a specific search string; thus providing greater versatility.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_regexp_like.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_regexp_like.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: regexp_like</atom:title>
  <atom:content type="html">Allows a like comparison using regular-expression.The source_string supports character datatypes (CHAR, VARCHAR2, CLOB, NCHAR, NVARCHAR2, and NCLOB but not LONG). The pattern parameter is another name for the regular expression. match_parameter allows optional parameters such as handling the newline character, retaining multiline formatting, and providing control over case-sensitivity.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_registry_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_registry_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: registry_get</atom:title>
  <atom:content type="html">Returns a current value of a registry settingregistry_get is used to retrieve values stored within database registry.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_registry_get_all.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_registry_get_all.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: registry_get_all</atom:title>
  <atom:content type="html">Returns a vector of all registry settingsThe function returns a vector of even length that contains two elements for every registry setting that is now stored in the database: the name and the current value of the setting. The order of &#39;name-value&#39; pairs in the resulting vector may vary from call to call. To search such a vector by a setting name, the vector can be passed as a second argument to the function get_keyword(). The returned vector is a full copy of the content of the registry. To change the actual registry, use registry_set.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_registry_name_is_protected.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_registry_name_is_protected.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: registry_name_is_protected</atom:title>
  <atom:content type="html">The function checks if a given registry variable is read-only or protected from occasional changes.Some registry variables are used solely by internal server routines so they should not be changed by any application. Some of these &quot;protected&quot; variables can be updated by DBA only (in built-in Virtuoso/PL routines) whereas some can not be updated by any Virtuoso/PL routine at all. The function gets a variable name as a parameter and returns zero if such a variable variable can be created/modified/removed by any application, one if a variable can be modified by DBA but can not be removed and two if the variable can not be altered even by DBA. The returned value does not indicate that the variable exists or not exists. The name of not yet existing variable can be protected anyway to prevent future misuse of an variable by an application.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_registry_set.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_registry_set.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: registry_set</atom:title>
  <atom:content type="html">Associates a value to the name in the Database registryThis associates a value to the name in the Database registry. The name should be a string and the value must be also string. Registry settings are kept in Database, therefore they are persistent. Some registry variables are used solely by internal server routines so they should not be set by any application. Some of these &quot;protected&quot; variables can be updated by DBA only (in built-in Virtuoso/PL routines) whereas some can not be updated by any Virtuoso/PL routine at all. If the function is called by DBA then a third argument can be specified to indicate how the function should try to update such a variable, but you will probably never use this feature.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_registry_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_registry_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: registry_remove</atom:title>
  <atom:content type="html">Remove a variable from registryThe function removes a given variable from registry, so future calls of registry_get returns zero. Some registry variables are used solely by internal server routines so they should not be changed by any application. Nobody can remove such a &quot;protected&quot; variable even if some of them can be updated by DBA.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repeat.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repeat.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repeat</atom:title>
  <atom:content type="html">returns a new string consisting of its string argument repeated a given number of times repeat returns a new string, composed of the string str repeated count times. If count is zero, an empty string &#39;&#39; is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_replace.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_replace.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: replace</atom:title>
  <atom:content type="html">This replaces every occurrence of the second argument in the first argument with the third argument. This replaces every occurrence of the second argument in the first argument with the third argument. The arguments can be narrow or wide strings.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_replay.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Backup<atom:link href="http://docs.openlinksw.com/virtuoso/fn_replay.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: replay</atom:title>
  <atom:content type="html">starts the roll forward of the given logThis starts a roll forward of the given log. The log may have been produced by normal transaction logging, backup or crash dump. Logs may not be transferred between databases and thus cannot be rolled forward anywhere except on the database that generated them. This function is for example useful after restoring a backup. It should be called for each archived transaction log produced since the backup, including and starting with the one that was current when the backup was made. The operation blocks until the roll forward is complete. Other clients are not affected.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_disconnect.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_disconnect.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_disconnect</atom:title>
  <atom:content type="html">terminates communication with a replication publisher This terminates any communication with the publisher. Any pending synchronization communication is disconnected and all subscribed publications are marked as &#39;OFF&#39;. The effect is reversed on a subscription by subscription basis by calling repl_sync for each.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_grant.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_grant.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_GRANT</atom:title>
  <atom:content type="html">grant privileges for subscription to a publicationThis function is used to grant privilege for subscription to a SQL account for particular publication. The DBA accounts always have right for subscription to all available publications.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_init_copy.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_init_copy.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_INIT_COPY</atom:title>
  <atom:content type="html">create initial subscription state This function is called on the subscriber to copy the current state of the elements of the publication from the publishing server. Copied data can include DAV collections, tables, procedures etc. Syncing the subscription using repl_sync will synchronize the subscription once it has been initialized with this function. The state copied corresponds to the state of the published data as of the last checkpoint completed on the publisher.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_new_log.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_new_log.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_new_log</atom:title>
  <atom:content type="html">create new publication log This function switches to a new file for logging data for the publication. If the file is NULL a new file name will be generated based on the previous file name by appending or replacing a datetime field in the file name.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_publish.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_publish.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_PUBLISH</atom:title>
  <atom:content type="html">create publication on publisher This function starts a publication and associates a file system file to it. The file will be used to log transaction records associated to the publication. The server will periodically start new files, so that replication log files do not grow indefinitely. New files will go to the same directory as the initial one and will have names suffixed with the date and time of their creation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_pub_add.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_pub_add.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_PUB_ADD</atom:title>
  <atom:content type="html">add item to a publicationThis function is used to add items to a pre-existing publication and to set replication options for the published items. Operations concerning the added item will henceforth be logged into the publication&#39;s log. Performing this operation will copy the item and optionally its definition to existing subscribers.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_pub_init_image.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_pub_init_image.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_PUB_INIT_IMAGE</atom:title>
  <atom:content type="html">create initial image of publication on publisherThe image creation process forces checkpoint and runs in atomic mode. If image_file_path does not contain path components (slashes or backslashes), image slices are stored in one of backup directories defined in virtuoso.ini using round-robin strategy. This function is used to create image of publication to be replayed on a subscribed upon initial setup. This can be used when publication data is so large to be copied via repl_init_copy() which uses VDB operations. The image file(s) created by this function must be loaded on subscriber with replay() function in order of their creation (if image is split on to a several files).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_pub_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_pub_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_PUB_REMOVE</atom:title>
  <atom:content type="html">remove item from publication.This function is used to remove an item from existing publication. It&#39;s action is performed on publisher side and depending of flag it can send replication message to subscribers to remove this from subscription.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_revoke.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_revoke.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_REVOKE</atom:title>
  <atom:content type="html">revoke privileges for subscriptionRevokes Privileges for Subscription. This is called on the publisher to revoke access to the publication from the user account on the publisher. The subscriber will no longer gain access to the publication with this account.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_sched_init.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_sched_init.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_SCHED_INIT</atom:title>
  <atom:content type="html">adds scheduled job to synchronize subscriptionsAdds scheduled job to synchronize all subscriptions. The server will attempt to start synchronization of all non-synchronized subscriptions at a 1 minute interval. The action can be reversed by deleting the corresponding row from the SYS_SCHEDULED_EVENTS table.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_server.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_server.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_SERVER</atom:title>
  <atom:content type="html">defines a server that will participate in replicationThis function defines a server that will participate in replication. The name is a symbolic name that should match the name specified as the ServerName configuration parameter in the replication section of the virtuoso.ini file of the server being defined. The address is the &lt;host:port&gt; where the server designated by the name is listening. The DSN is an ODBC data source name referring to the server, so that the subscriber can retrieve schema and other information. Note that replication communication itself does not take place through ODBC but that ODBC access to the publisher is required to initiate the subscription. In order to subscribe to publications from a server the server must first be declared with this function. If this function is called to define the local server, i.e. the given server name is the ServerName in the Replication section of the local ini file the function has no effect.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_server_rename.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_server_rename.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_server_rename</atom:title>
  <atom:content type="html">rename the publishing server instance This function is useful to rename the publishing servers data (that stored in to the replication tables) after renaming the server in virtuoso.ini file. The call of the procedure will associate the all data belong to the old server name to the current server name. It will also set the appropriate transaction levels. In case of duplicate publications (publications with the same name exists in old and new server definitions) it will reject the operation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_stat.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_stat.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_STAT</atom:title>
  <atom:content type="html">retrieve status of all subscriptions and publicationsRetrieves status of all subscriptions and publications. This function is for interactive use (via ISQL tool).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_status.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_status.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_status</atom:title>
  <atom:content type="html">returns status of a published or subscribed publicationGiven a publisher and publication name this returns the status of the publication on the local server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_subscribe.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_subscribe.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_SUBSCRIBE</atom:title>
  <atom:content type="html">add a subscriptionThis function is used to subscribe to an existing publication, and to specify the local WebDAV owner for replicated WebDAV content. Before making a subscription the repl_server() function must be called in order to define the publishing server. After making a subscription it becomes off-line awaiting synchronization from a scheduled task or call to the repl_sync() function. Also the initial data of the subscription will be not loaded until repl_init_copy() is called or the initial image has been loaded.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_sync.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_sync.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_sync</atom:title>
  <atom:content type="html">starts the syncing process against an existing subscription This starts the syncing process against an existing subscription. The function returns as soon as the request has been successfully sent. The synchronization will take place in the background. If the syncing process is already underway or if the subscriber is already in sync and connected to the publisher this function has no effect. If there is no connection to the publisher at the time of calling this function and the connection fails and an error is immediately signalled. To initiate a synchronization a valid SQL account must be specified. Also the account must have rights to the publication unless publisher DBA&#39;s account is used to connect.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_sync_all.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_sync_all.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_sync_all</atom:title>
  <atom:content type="html">synchronize all subscriptionsThis function is used to synchronize all subscriptions. It make a synchronization requests to the all publisher and will return immediately after that. The status of subscriptions can be tested with repl_stat() function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_text.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_text.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_text</atom:title>
  <atom:content type="html">adds a SQL statement to the log of the replicationThis SQL function adds the SQL statement to the log of the publication. The statement will typically be a procedure call but can be any SQL statement. There can be a parameters, which are bound to ?&#39;s in the statement&#39;s text from left to right. There is no restriction on the number of parameters.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_this_server.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_this_server.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_this_server</atom:title>
  <atom:content type="html">returns calling servers name</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_unpublish.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_unpublish.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_UNPUBLISH</atom:title>
  <atom:content type="html">drop publication on publisher This function is used to remove from current replication set an existing publication. The replication messages for all existing items will be stopped, so the last replication message will instruct the subscribers that this publication is dropped. On subscriber side depending of the copy mode of items they can be removed or not, but the description entry for that publication will be removed explicitly. Any existing grants to the publication being dropped will be revoked.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_unsubscribe.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_unsubscribe.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_UNSUBSCRIBE</atom:title>
  <atom:content type="html">drop subscriptionThis function is used to stop receiving a replication messages from a publisher server for a item or whole subscription. It will be invoked automatically when a publication is dropped. The subscriber can also invoke this function to stop receiving replication messages. The existing items can be dropped or not depending on the copy mode flag. The description entries for that subscription will be removed. There is no &quot;undo&quot; ability. To temporally halt the replication messages you can use repl_disconnect().</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_repl_purge.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_repl_purge.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: repl_purge</atom:title>
  <atom:content type="html">purges transactional replication logs for specified account This procedure purges transactional replication logs for specified account. Logs whose start replication level lags more than REPL_MAX_DELTA (1000000000) transactions behind current replication level of a specified account are removed. After repl_purge() is finished next repl_purge() run is scheduled using SYS_SCHEDULED_EVENT facility. Account sync requests from subscribers are delayed while repl_purge() is running for this account.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_CREATE_SNAPSHOT_PUB.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_CREATE_SNAPSHOT_PUB.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_CREATE_SNAPSHOT_PUB</atom:title>
  <atom:content type="html">Create bi-directional snapshot publicationThis procedure should be used to create a bi-directional snapshot publication. If the item parameter is a table then this procedure creates an updateable snapshot log and generates an updating procedure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_CREATE_SNAPSHOT_SUB.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_CREATE_SNAPSHOT_SUB.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_CREATE_SNAPSHOT_SUB</atom:title>
  <atom:content type="html">Create bi-directional snapshot subscription to an existing publication.This procedure should be used to create a bi-directional snapshot subscription.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_DROP_SNAPSHOT_SUB.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_DROP_SNAPSHOT_SUB.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_DROP_SNAPSHOT_SUB</atom:title>
  <atom:content type="html">Drops a subscription to a bi-directional snapshot publicationThis procedure drops a subscription to a snapshot publication.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_DROP_SNAPSHOT_PUB.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_DROP_SNAPSHOT_PUB.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_DROP_SNAPSHOT_PUB</atom:title>
  <atom:content type="html">Drop bi-directional snapshot publicationThis procedure drops a snapshot publication.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_INIT_SNAPSHOT.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_INIT_SNAPSHOT.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_INIT_SNAPSHOT</atom:title>
  <atom:content type="html">Initializes a bi-directional snapshot publicationThis procedure should be used to initialize a bi-directional snapshot publication. Note: This function should be run on publisher.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_UPDATE_SNAPSHOT.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_UPDATE_SNAPSHOT.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_UPDATE_SNAPSHOT</atom:title>
  <atom:content type="html">Updates a bi-directional snapshot publicationThis procedure should be used to update a bi-directional snapshot publication. This procedure pulls all the updates from subscribers (with conflict resolution) and then pushes all the updates from publisher to all the subscribers.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_SNP_SERVER.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_SNP_SERVER.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_SNP_SERVER</atom:title>
  <atom:content type="html">Define bi-directional snapshot replication server nameThis function should be used to define a server for bi-directional snapshot replication.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_SERVER_NAME.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_SERVER_NAME.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_SERVER_NAME</atom:title>
  <atom:content type="html">Return bi-directional snapshot replication server name for specified DSNThis function should be used to determine bi-directional snapshot replication server name.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_ADD_CR.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_ADD_CR.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_ADD_CR</atom:title>
  <atom:content type="html">Creates conflict resolver for bi-directional transactional replicationSimple conflict resolvers can be generated by calling this function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_ADD_DAV_CR.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_ADD_DAV_CR.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_ADD_DAV_CR</atom:title>
  <atom:content type="html">Creates conflict resolver for bi-directional replication in DAVSimple conflict resolvers for DAV bi-directional replication can be generated by calling this function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_REPL_ADD_SNAPSHOT_CR.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_REPL_ADD_SNAPSHOT_CR.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: REPL_ADD_SNAPSHOT_CR</atom:title>
  <atom:content type="html">Creates conflict resolver for bi-directional replicationSimple conflict resolvers can be generated by calling this function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_result.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_result.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: result</atom:title>
  <atom:content type="html">Sends one row of results to the calling client.The result_names() predefines variables to be used in a result set to follow. The variables must be previously declared, from which the column data types are ascertained. This assigns the meta data but does not send any results. The result() function sends its parameters as a single row of results. These parameters should be compatible with those in the previous result_names(). The end_results() function can be used to separate multiple result sets. The result_names() can then be used to alter the structure of the next result set. The result_names() call can be omitted if the application already knows what columns and their types are to be returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_result_names.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_result_names.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: result_names</atom:title>
  <atom:content type="html">The result_names() predefines variables to be used in a result set to follow. The variables must be previously declared, from which the column data types are ascertained. This assigns the meta data but does not send any results. The result() function sends its parameters as a single row of results. These parameters should be compatible with those in the previous result_names(). The end_results() function can be used to separate multiple result sets. The result_names() can then be used to alter the structure of the next result set. The result_names() call can be omitted if the application already knows what columns and their types are to be returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rexecute.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rexecute.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rexecute</atom:title>
  <atom:content type="html">execute a SQL statement on a remote DSNThis function can be used to execute SQL on a remote data source directly. The result_set parameter is useful for obtaining a result-set quickly and easily. However, if the result-set is going to be large, this comes at a cost in terms of time and resources, particularly memory, since Virtuoso will have to obtain all results from the statement and build the result-set arrays in memory before returning back to the caller. A more efficient way is to obtain a cursor handle and iterate through the result set one row at a time:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rstmtexec.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rstmtexec.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rstmtexec</atom:title>
  <atom:content type="html">execute a SQL statement on a remote DSN, provides a result set where applicable.This function can be used to execute SQL on a remote data source directly. It returns a result set where one is expected. This function is wrapper for the rexecute() provided for convenience as a shortcut. Unless explicitly granted, only the DBA group is permitted to use the rstmtexec() to maintain security. Caution is required here since any user granted use of rstmtexec() has full control of the remote data source set-up by the DBA, albeit limited to the overall abilities of the remote user on the remote data source. Users can be granted and denied access to this function using the following commands:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_right.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_right.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: right</atom:title>
  <atom:content type="html">get n rightmost characters of a stringright returns the count rightmost characters of string str. If count is zero an empty string &#39;&#39; is returned. If length of str is less than count then a copy of the whole str is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rmoreresults.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rmoreresults.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rmoreresults</atom:title>
  <atom:content type="html">move to next result set of rexecute()This function moves to the next result set when handling result sets returned by statement executed with rexecute.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rnd.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rnd.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rnd</atom:title>
  <atom:content type="html">returns a random number between 0 and n - 1 inclusive The rnd function returns a random number between zero and n - 1, inclusive. randomize initializes the random number generator. The random number generator is initialized after the clock at first usage, so the produced sequences will be different each time unless specifically initialized.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rnext.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rnext.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rnext</atom:title>
  <atom:content type="html">Get next result from a remote result setUse rnext in combination with rmoreresults to iterate over a result set produced by a statement run in a remote data source with rexecute.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_row_count.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_row_count.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: row_count</atom:title>
  <atom:content type="html">returns number of rows affected by the previous DML statement in a procedure bodyThis function returns the count of rows affected by the previous DML statement in a procedure body. The scope is local to the procedure. Calling this from ODBC will always return 0. This is the PL equivalent of the SQLRowCount ODBC function. The count is set after any in-line searched or positioned update, insert or delete. This is also set by the exec function. The count stays set until overwritten by the next DML operation. This is not set by rexecute.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_rtrim.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_rtrim.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: rtrim</atom:title>
  <atom:content type="html">trims given characters from right of given string ltrim returns a copy of subsequence of string str with all the characters present in trimchars trimmed off from the beginning. If the second argument is omitted, it is a space &#39; &#39; by default. rtrim is similar except that it trims from the right. trim trims from both ends.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_search_excerpt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_search_excerpt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: search_excerpt</atom:title>
  <atom:content type="html">Returns excerpts with hit words from textThis function produces representative samples for use in displaying a query hit. There are two modes: html mode and text mode. In html mode everything looks like html tags is ignored and searching of excerpt begins from &lt;body&gt; tag. All found hit words highlighted by html_hit_tag. In text mode text is treated as plain text, html tag detection is disabled and hit words is not highlighted.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_second.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_second.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: second</atom:title>
  <atom:content type="html">get second from a datetimesecond takes a datetime and returns an integer containing a number representing the second of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sequence_get_all.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sequence_get_all.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sequence_get_all</atom:title>
  <atom:content type="html">Returns a vector of states of all sequence objectsThe function returns a vector of even length that contains two elements for every sequence object that is now stored in the database: the name and the current state. The order of &#39;name-state&#39; pairs in the resulting vector may vary from call to call. To search such a vector by a setting name, the vector can be passed as a second argument to the function get_keyword(). Changes in the returned vector will not alter sequence objects of the database. To change actual sequence objects, use sequence_set().</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sequence_next.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sequence_next.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sequence_next</atom:title>
  <atom:content type="html">Returns the current state of the specified sequence and increments it by one.This function returns the current state of the specified sequence and atomically increments it by one. The next call will thus return a number one greater than the previous. The sequence is shared between all connections and all transactions so an increment that is is made in one of connection will be seen in other connection immediately. Using a sequence never involves locking.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sequence_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sequence_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sequence_remove</atom:title>
  <atom:content type="html">Removes a sequence objectThe function removes a sequence object created before by sequence_set or sequence_next.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sequence_set.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sequence_set.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sequence_set</atom:title>
  <atom:content type="html">Sets and returns the state of a sequence object. The function sets and returns the state of a sequence object. The mode specifies whether a check for order of values should be made. If mode equals 0, the state is set regardless of the previous state. If mode is non-zero, the state is changed only if the new state is greater than the previous state. This gives some (weak) protection from occasional &#39;rewind&#39; the sequence back to values that are already in use.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_serialize.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_serialize.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: serialize</atom:title>
  <atom:content type="html">convert any heterogeneous array or tree of arrays into a binary string and back These functions will convert any heterogeneous array or tree of arrays into a binary string and back. The format is platform independent. is the identity function. These functions are useful for persisting heterogeneous arrays.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_serialize_to_UTF8_xml.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_serialize_to_UTF8_xml.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: serialize_to_UTF8_xml</atom:title>
  <atom:content type="html">Converts argument to its UTF-8 string representation.The function converts its argument to a narrow string in UTF-8 encoding. The way conversion is done depends on the type of the argument. If value is a wide (national) string or a LONG NVARCHAR then it is directly converted to UTF-8 string. If value is a string or a LONG VARCHAR then it is converted from current charset of client connection to the UTF-8.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_serv_queue_top.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_serv_queue_top.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: SERV_QUEUE_TOP</atom:title>
  <atom:content type="html">Retrieve target website and store within VirtuosoWeb Robot site retrieval can be performed with the WS.WS.SERV_QUEUE_TOP PL function integrated in to the Virtuoso server. To run multiple walking robots all you simply need to do is kick them off from separate ODBC/SQL connections and all robots will walk together without overlapping. From a VSP interface, after calling the retrieval function you may call http_flush to keep running tasks in the server and allowing the user agent to continue with other tasks.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ses_connect.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ses_connect.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ses_connect</atom:title>
  <atom:content type="html">Opens a TCP session and returns its handle.This function requires dba privileges. This function is used to establish a new TCP connection to the target host. It returns a special datatype which represents the session handle.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ses_disconnect.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ses_disconnect.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ses_disconnect</atom:title>
  <atom:content type="html">Disconnections a TCP session.This function is used to disconnect from a session and destroy the session handle. After this function is called the session handle becomes invalid and hence cannot be used for reading or writing as an error will occur.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ses_read_line.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ses_read_line.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ses_read_line</atom:title>
  <atom:content type="html">Read a line of character data from a TCP session.This function is used to read a line of character data from an open TCP session. This function will read characters until it reaches an end of line up to a maximum of 1024 characters. The session can be passed as a session_handle. If the session_handle is omitted then execution is in current session/VSP context and will read from the open HTTP session. Ses_read_line() will suspend execution while attempting to read from the session until the timeout period of 100 seconds expires. When the timeout expires an error will be produced to indicate that the operation was unsuccessful.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ses_write.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ses_write.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ses_write</atom:title>
  <atom:content type="html">Write character data to an open TCP session.This function is used to write character data taken from the buffer parameter to an open TCP session. Attempts to write to a close session will result in an error being returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_set_row_count.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_set_row_count.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: set_row_count</atom:title>
  <atom:content type="html">sets the affected rows counter in the current context or in the context of the callerThe function set_row_count () is used to set the affected rows counter in the current context or in the context of the caller. Therefore it can be used to set the affected rows counter (returned by row_count()) in places where an instead of trigger is used. If result of decrement of the affected rows counter is an negative integer it will be set to zero.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_set_user_id.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_set_user_id.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: set_user_id</atom:title>
  <atom:content type="html">sets the current user for executionThis function changes the effective user and group to that of the user defined by user_name parameter. When called by a user with DBA group privileges, the optional password may be omitted. Otherwise it has to be the valid password for user_name. The mode parameter determines persistence (context) of effects of the call: If omitted or set to integer value 1, the effective user privileges will remain in effect within current stored procedure context only - upon returning, the effective user privileges will be automatically reset to state effective before set_user_id. When mode is equal to integer value 0, the effective user privileges will remain set for duration of current ODBC session, current request in web server context, or until next call of set_user_id. This function is analogous to the UNIX &#39;su&#39; command.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_set_identity_column.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_set_identity_column.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: set_identity_column</atom:title>
  <atom:content type="html">sets the sequence starting value for an identity columnThis function takes the table name, the column name and the new sequence value as parameters. It checks for the existence of the identity column, and then sets the sequence value (using the sequence_set) and returns the old sequence value. The table and column names must be properly qualified to ensure the correct resource is located. The effect of calling this function is immediate.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sign.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sign.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sign</atom:title>
  <atom:content type="html">returns -1, 0, or 1 depending on the sign of its numerical sign returns either -1, 0 or 1 depending whether its numeric argument is negative, zero or positive.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_signal.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_signal.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: signal</atom:title>
  <atom:content type="html">Signal an exception in the calling procedure This signals the given SQLSTATE with the message. The calling procedure will transfer control to the most appropriate local handler. In the absence of a local handler the procedure terminates and signals the exception in the scope where it was called from, until there either is a handler or there are no more calling procedures. If there is no handler in the entire stack of call contexts the error is signalled to the client. Handlers can be declared with whenever .. goto and the declare handler for construct. See the Virtuoso/PL documentation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sinv_create_key_mapping.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sinv_create_key_mapping.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sinv_create_key_mapping</atom:title>
  <atom:content type="html">Creates a key mapping function &amp; table (as described in the doc section SQL Inverse Functions).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sinv_create_inverse.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sinv_create_inverse.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sinv_create_inverse</atom:title>
  <atom:content type="html">Creates inverse mapping for the mentioned functions (as described in the doc section SQL Inverse Functions).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sinv_drop_inverse.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sinv_drop_inverse.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sinv_drop_inverse</atom:title>
  <atom:content type="html">Reverses the effect of sinv_create_inverse procedure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_smime_sign.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_smime_sign.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: smime_sign</atom:title>
  <atom:content type="html">Converts a MIME message to a signed S/MIME message</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_smime_verify.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_smime_verify.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: smime_verify</atom:title>
  <atom:content type="html">Verifies signature of signed MIME message This function takes the RFC822 text of an e-mail containing an S/MIME signed message and verifies it&#39;s signature using the CA certificates in certs, which is an array of strings containing single or multiple PEM-encoded certificates.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_smtp_send.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_smtp_send.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: smtp_send</atom:title>
  <atom:content type="html">send message to SMTP serverVirtuoso can act as an SMTP client. This means that Virtuoso is able to send emails directly to a mail SMTP server. Virtuoso has a simple function to facilitate this. This can be called from stored procedures, VSP pages, triggers etc. The sender and recipient email addresses must be enclosed with &lt;..&gt; and separated by commas i.e. string &#39;&lt;support@openlinksw.co.uk&gt;,&lt;sales@openlinksw.co.uk&gt;&#39; The message Body contains headers such as Subject, From, To, Cc, Bcc and then continues with the actual message text itself. New lines can be added using &#39;\r\n&#39;</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_box_xml_entity.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_box_xml_entity.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_box_xml_entity</atom:title>
  <atom:content type="html">Converts an XML entity to an SQL value given the desired SQL type. This function converts an XML entity to an SQL value based on the type of the entity and the desired SQL type. This function is called internally to convert a SOAP request parameter to a PL procedure parameter when a SOAP request is being processed by the SOAP server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_dt_define.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_dt_define.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_dt_define</atom:title>
  <atom:content type="html">define re-define or erase the complex datatype definition for SOAP callsThis defines a new complex SOAP datatype (usually array of structure) named &#39;name&#39;. The schema_string string represents definition as complexType element from XML Schema. The only complexContent, all and sequence elements can be used within the complexType. This means that optional elements in the defined datatype are not supported as a variant of the SOAP parameter datatype. If the schema descriptions contains an unsupported element , the SQL error will be signalled and error message will explain what element is wrong.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_call.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_call.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_call</atom:title>
  <atom:content type="html">calls a function from a SOAP server and returns the result. value; deprecated, use SOAP_CLIENT () instead This calls a function from a SOAP server and returns the result as a return value. Params is an array of (Parameter name, Value) pairs representing the parameters passed in the SOAP call. Each of these pairs become an XML sub-entity of the procedure entity. The return value of the function is the entity inside the SOAP body of the response. In debug mode the return value is an array of 3 elements; the non-debug return value (if any) as element 0, the XML text of the request as element 1 and the XML text of the server response as element 2. This function does not use any XML types when creating the XML. It represents types as a cast to varchar would, with one exception - dates and times according to ISO8061. The Virtuoso SOAP client can work with complex datatypes, in which case the parameters array must conform to the following convention: This will cause type checking and validation of the values to be encoded for SOAP request.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_client.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_client.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_client</atom:title>
  <atom:content type="html">Invoke a SOAP service and returns result value.This will invoke the specified SOAP service.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_make_error.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_make_error.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_make_error</atom:title>
  <atom:content type="html">Creates a SOAP error reply XML message based on its parameters. This function creates a SOAP error reply based on the given parameters. It returns the generated XML as a varchar value.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_print_box.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_print_box.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_print_box</atom:title>
  <atom:content type="html">Formats an SQL value and returns it as a generated XML fragment. This function formats an SQL value as an XML fragment and returns it. This is used internally by the SOAP server to encode the output parameter values and return values when processing a SOAP request.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_sdl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_sdl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_sdl</atom:title>
  <atom:content type="html">Generate SDL document for a PL module and return it as a varchar.This function generates a SDL for the procedures in a PL module the same way as /SOAP/services.xml is generated for the procedures in WS.SOAP.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_server.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_server.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_server</atom:title>
  <atom:content type="html">Execute SOAP request and return XML reply as a varchar. This function executes the SOAP request in the same way as it it was directed to the /SOAP physical path. It returns the XML SOAP reply as a varchar value.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_wsdl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_wsdl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_wsdl</atom:title>
  <atom:content type="html">Generate WSDL document for a PL module and return it as a varchar. This function generates WSDL for the procedures in a PL module the same way as /SOAP/services.wsdl is generated for the procedures in WS.SOAP.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_wsdl_import.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_wsdl_import.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_wsdl_import</atom:title>
  <atom:content type="html">The soap_wsdl_import() function is used to import operations and types definitions from an WSDL file on a remote server. The retrieved file will be parsed and PL (procedure language) wrappers will be generated for each SOAP operation that is described. The SOAP service will be represented by a PL module which will be the overall container the generated PL wrappers. Once the WSDL file has been imported the PL wrappers are automatically generated and available for use.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_box_structure.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_box_structure.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_box_structure</atom:title>
  <atom:content type="html">This function provides a way to encapsulate a structure suitable for soap serialization. It accepts a name/value pairs which represents name and value of elements of a structure. For example structure : will be represented as soap_box_structure (&#39;varString&#39;, &#39;hello&#39;, &#39;varInt&#39;, 1234); furthermore value returned from soap_box_structure passed as an output parameter to the procedure (named structname) working as SOAP method will return :</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_soap_current_url.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_soap_current_url.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: soap_current_url</atom:title>
  <atom:content type="html">Returns URL used to access particular HTTP resource. This function is used to get in VSP/VSPX context the URL used to access current resource (page). It check whether &#39;Host&#39; header field is specified, if not will return as a host information the IP address resolved via connected socket information.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_space.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_space.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: space</atom:title>
  <atom:content type="html">returns a new string of count spacesspace returns a new string, composed of count spaces. If count is zero, an empty string &#39;&#39; is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_split_and_decode.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Encoding &amp; Decoding<atom:link href="http://docs.openlinksw.com/virtuoso/fn_split_and_decode.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: split_and_decode</atom:title>
  <atom:content type="html">converts escaped var=val pairs to a vector of strings split_and_decode converts the escaped var=val pair inputs text to a corresponding vector of string elements. If the optional third argument is a string of less than three characters, then does only the decoding (but no splitting) and returns back a string.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sprintf.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sprintf.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sprintf</atom:title>
  <atom:content type="html">returns a formatted stringsprintf returns a new string formed by &quot;printing&quot; a variable number of arguments arg_1 - arg_x according to the format string format, that is, exactly the same way as with the sprintf function of C language. However the sprintf function enforces some additional limitations over the sprintf C function. It does not allow for single value output to take more than 2000 characters. It does support the following additional format characters: diouxXeEfgcs - as in the C language printf S - as &#39;s&#39; but escapes the single quotes by doubling them (as per SQL/92). This is suitable for constructing dynamic SQL statements with string literals inline.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sprintf_inverse.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sprintf_inverse.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sprintf_inverse</atom:title>
  <atom:content type="html">returns vector on a specified pattern.sprintf_inverse gets a string to parse, a format string and an integer (0,1 or 2) that indicates error recovery method. If the first argument matches the format string then it returns vector of the pattern values.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sprintf_iri.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sprintf_iri.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sprintf_iri</atom:title>
  <atom:content type="html">returns a formatted string that is marked as an IRI string.sprintf_iri is similar to sprintf and returns a new string formed by &quot;printing&quot; a variable number of arguments arg_1 - arg_x according to the format string format. The difference is that the returned string is marked as being IRI string so some applications and clients may distinguish between RDF reference string and RDF literal.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sprintf_iri_or_null.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sprintf_iri_or_null.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sprintf_iri_or_null</atom:title>
  <atom:content type="html">returns a formatted IRI string or null if any of the arguments except the first is null.sprintf_iri_or_null is similar to sprintf_iri and returns a new string formed by &quot;printing&quot; a variable number of arguments arg_1 - arg_x according to the format string format. The difference is that the function can return null if any of the arguments except the first one is null. The returned string is marked as being IRI string so some applications and clients may distinguish between RDF reference string and RDF literal.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sprintf_or_null.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sprintf_or_null.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sprintf_or_null</atom:title>
  <atom:content type="html">returns a formatted string or null if any of the arguments except the first is null.sprintf_or_null is similar to sprintf and returns a new string formed by &quot;printing&quot; a variable number of arguments arg_1 - arg_x according to the format string format. The difference is that the function can return null if any of the arguments except the first one is null.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_columns.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_columns.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_columns</atom:title>
  <atom:content type="html">get column information from table on a remote DSNThis function corresponds to the ODBC catalog call of similar name. It and related functions are used by the virtual database to query remote data dictionaries. The dsn argument must refer to a dsn previously defined by vd_remote_data_source or ATTACH TABLE. For instance, the qualifier argument corresponds to the szTableQualifier and cbTableQualifier arguments of an ODBC catalog function. The SQL NULL value corresponds to the C NULL value. The arguments can contain % signs, which are interpreted as in LIKE.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_data_sources.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_data_sources.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_data_sources</atom:title>
  <atom:content type="html">get list of available DSNssql_data_sources is used to get the list of datasources available to the dsn. It returns a vector of 2 element vectors containing Data source name and type pairs.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_gettypeinfo.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_gettypeinfo.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_gettypeinfo</atom:title>
  <atom:content type="html">return type information from a remote DSNYou can use the functions described here to find out information about the remote datasources that you are using. These could be especially useful in Virtuoso PL later on if you are not able to know everything about the remote tables ahead of time for the ATTACH TABLE statement. statement These SQL functions correspond to the ODBC catalog calls of similar name. The dsn argument must refer to a dsn previously defined by vd_remote_data_source or ATTACH TABLE.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_primary_keys.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_primary_keys.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_primary_keys</atom:title>
  <atom:content type="html">get primary key information about a table on a remote DSNYou can use the functions described here to find out information about the remote datasources that you are using. These could be especially useful in Virtuoso PL later on if you are not able to know everything about the remote tables ahead of time for the ATTACH TABLE statement. statement These SQL functions correspond to the ODBC catalog calls of similar name. These are used to access the data dictionary of remote data sources inside the ATTACH TABLE process. The dsn argument must refer to a dsn previously defined by vd_remote_data_source or ATTACH TABLE.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_statistics.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_statistics.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_statistics</atom:title>
  <atom:content type="html">retrieve statistics information on remote DSNThis SQL function corresponds to the ODBC catalog call of similar name. It is used to access the data dictionary of remote data sources inside the ATTACH TABLE process. The dsn argument must refer to a dsn previously defined by vd_remote_data_source or ATTACH TABLE. The qualifier argument corresponds to the szTableQualifier and cbTableQualifier arguments of an ODBC catalog function. A SQL NULL value corresponds to the C NULL value. The arguments can contain % signs, which are interpreted as in LIKE.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_tables.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_tables.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_tables</atom:title>
  <atom:content type="html">get list of tables from remote DSNThis function corresponds to the ODBC catalog call of similar name. It and related functions are used by the virtual database to query remote data dictionaries. The dsn argument must refer to a dsn previously defined by vd_remote_data_source or ATTACH TABLE. The qualifier argument corresponds to the szTableQualifier and cbTableQualifier arguments of an ODBC catalog function. A SQL NULL value corresponds to the C NULL value. The arguments can contain % signs, which are interpreted as in LIKE.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_special_columns.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_special_columns.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_special_columns</atom:title>
  <atom:content type="html">get special column information from table on a remote DSNThis function corresponds to the ODBC catalog call of similar name. It and related functions are used by the virtual database to query remote data dictionaries. First argument of the ODBC SQLSpecialColumns is always SQL_BEST_ROWID. The dsn argument must refer to a dsn previously defined by vd_remote_data_source() or ATTACH TABLE.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_procedures.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_procedures.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_procedures</atom:title>
  <atom:content type="html">get procedures information for a remote DSNThis function corresponds to the ODBC catalog call of similar name. It and related functions are used by the virtual database to query remote data dictionaries. The dsn argument must refer to a dsn previously defined by vd_remote_data_source() or ATTACH TABLE. For instance, the qualifier argument corresponds to the szTableQualifier and cbTableQualifier arguments of an ODBC catalog function. The SQL NULL value corresponds to the C NULL value. The arguments can contain % signs, which are interpreted as in LIKE.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_write_private_profile_string.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_write_private_profile_string.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_write_private_profile_string</atom:title>
  <atom:content type="html">Sets a DSN&#39;s attribute valueThis function corresponds to the ODBC catalog call of similar name. It and related functions are used by the virtual database to query remote data dictionaries. The type argument must be either &#39;system&#39; or &#39;user&#39;. Sets a data source attribute by calling SQLWritePrivateProfileString from the ODBC Installer API.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_get_private_profile_string.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_get_private_profile_string.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_get_private_profile_string</atom:title>
  <atom:content type="html">Gets the DSN&#39;s attributes listThis function corresponds to the ODBC catalog call of similar name. It and related functions are used by the virtual database to query remote data dictionaries. The type argument must be either &#39;system&#39; or &#39;user&#39;. Gets the data source attributes by calling SQLGetPrivateProfileString from the ODBC Installer API.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_config_data_sources.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_config_data_sources.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_config_data_sources</atom:title>
  <atom:content type="html">Configures a remote DSN as in the DSN attribute stringThis function creates or modifies a user or system data source based on the semicolon separated list of DSN attributes. The type argument must be either &#39;system&#39; or &#39;user&#39;. Configures the data source by calling SQLWriteDSNToIni/SQLWritePrivateProfileString/SQLSetConfigMode from the ODBC Installer API.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_get_installed_drivers.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_get_installed_drivers.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_get_installed_drivers</atom:title>
  <atom:content type="html">get column information from table on a remote DSNThis function corresponds to the ODBC Installer call of similar name. It and related functions are used by the virtual database to query remote data sources.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_remove_dsn_from_ini.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_remove_dsn_from_ini.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_remove_dsn_from_ini</atom:title>
  <atom:content type="html">removes a DSN from the ODBC registryThis function corresponds to the ODBC installer call of similar name. It and related functions are used by the virtual database to handle remote data sources.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_transact.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_transact.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_transact</atom:title>
  <atom:content type="html">get list of available DSNsThis procedure can be used to control the commit/rollback behavior of a particular remote data source during a Virtuoso transaction such as in a stored procedure. Under normal circumstances Virtuoso will correctly commit or rollback all associated work as expected, however it may be desirable intervene. When issued without the second parameter a commit will be forced upon the current transactions of the dsn_name above the call to sql_transact regardless of overall outcome. When rollback = 1 is set then a rollback will be forced likewise, hence this will not rollback work on the remote dsn_name prior to sql_transact.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_write_file_dsn.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_write_file_dsn.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_write_file_dsn</atom:title>
  <atom:content type="html">Creates a new file DSNThis function calls the SQLWriteFileDSN as follows : SQLWriteFileDSN (dsn, &#39;ODBC&#39;, string, value)</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sql_driver_connect.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sql_driver_connect.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sql_driver_connect</atom:title>
  <atom:content type="html">Tries connecting using supplied connection stringThis function calls SQLDriverConnect with the supplied connection string and immediately disconnects after the call.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sqrt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sqrt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sqrt</atom:title>
  <atom:content type="html">calculate square rootsqrt calculates the square root of its argument and returns it as a IEEE 64-bit float.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_status.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_status.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: status</atom:title>
  <atom:content type="html">Returns statistics for a running server as a result setDepending of input parameter displays a statistics for running server. Note that counters reported by status will be reset after server startup.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_key_estimate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_key_estimate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: key_estimate</atom:title>
  <atom:content type="html">Get an estimate of row count for a given set of leading index key partsGiven a table and an index, this function takes a random sample of the index, with the first key part equal to the third argument, the second equal to the fourth argument and so on. If only the table and index are given, the returned value is the approximate count of the entire index. Normal cast rules are applied to convert the arguments to the types of the corresponding key parts. If the cast fails, -1 is returned. The estimates are typically within 10% of the real count. If there have been random deletions or inserts leading to uneven page filling or if index entries are of greatly varying $ length, the estimates may be less precise.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_strcasestr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_strcasestr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: strcasestr</atom:title>
  <atom:content type="html">case-insensitive substring searchstrcasestr performs a case-insensitive substring search, returning a zero-based index pointing to beginning of first occurrence of sub or NULL if not found.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_strchr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_strchr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: strchr</atom:title>
  <atom:content type="html">strchr returns a zero-based index to the first occurrence of the character. strchr returns a zero-based index to the first occurrence of char. If char is not found NULL is returned. char can be given either as an integer ASCII value or a string, in which case the first character of that string is searched fo.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_stringdate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_stringdate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: stringdate</atom:title>
  <atom:content type="html">Convert a string to a datetimestringdate converts dates and timestamps from text to the internal DATETIME type. The external format is: YYYY.MM.DD hh:mm.ss uuuuuu where uuuuuu represents number of microseconds. If trailing parts are omitted from the string given to stringdate, they are assumed to be zero. The three first parts are mandatory. Note that use of cast (x as datetime) is preferred over this function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_stringtime.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Date &amp; Time Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_stringtime.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: stringtime</atom:title>
  <atom:content type="html">converts string to a timeConverts the argument to a time. Same as</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_string_output.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_string_output.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: string_output</atom:title>
  <atom:content type="html">make a string output streamA string output stream is a special object that may be used to buffer arbitrarily long streams of data. They are useful for handling data that would not otherwise fit within normal varchar size limitations. The HTTP output functions optionally take a string output stream handle as a parameter and then output to said stream instead of the HTTP client. A string output stream can be assigned to a database column in insert or update, causing the characters written to the stream to be assigned to the column as a narrow string. The function string_output_string can be used to produce a varchar out of a string output stream. It may be called repeatedly to obtain several copies of the data. http_rewrite can be used to flush a string output stream. If a string output stream is passed to the function result the data stored in it is sent to the client.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_string_output_flush.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_string_output_flush.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: string_output_flush</atom:title>
  <atom:content type="html">resets the state of the string_output object This function resets the state of the string output object. The string associated with the string output is dropped and is of 0 characters after this call.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_string_output_gz_compress.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Compression<atom:link href="http://docs.openlinksw.com/virtuoso/fn_string_output_gz_compress.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: string_output_gz_compress</atom:title>
  <atom:content type="html">compress a string_output with gzip algorithmThe string_output_gz_compress compresses its string_output argument using the gzip algorithm and writes the result to another string_output given as an argument. When successful, the number of bytes written to str_out_out is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_string_output_string.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_string_output_string.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: string_output_string</atom:title>
  <atom:content type="html">produce a string out of a string output streamThis function is used to produce a string from contents of a string output stream. See string_output for more information about string output streams.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_string_to_file.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_string_to_file.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: string_to_file</atom:title>
  <atom:content type="html">writes a varchar to a fileThis function requires dba privileges. string_to_file writes a varchar value or string session to a file. The path is relative to the server&#39;s working directory. The mode is an integer value interpreted as a position. A mode of 0 writes the content starting at offset 0. A mode of -1 appends to the end of the file. The append option is probably the most useful for producing application level logs, etc. The string argument can also be a string output object. In this case the content is used as the string.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_strrchr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_strrchr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: strrchr</atom:title>
  <atom:content type="html">returns a zero-based index to the last occurrence of the char in str. strchr returns a zero-based index to the last occurrence of char in string. If char is not found NULL is returned. char can be given either as an integer ASCII value or a string, in which case the first character of that string is searched for in str.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_strstr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_strstr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: strstr</atom:title>
  <atom:content type="html">substring searchstrcasestr performs a substring search, returning a zero-based index pointing to beginning of first occurrence of sub or NULL if not found.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_subseq.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_subseq.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: subseq</atom:title>
  <atom:content type="html">returns substring of a string or sub-vector of a vectorsubseq returns a copy of subsequence of string or vector str using zero-based indices from (inclusive) and to (exclusive) to delimit the substring or the vector extracted. If to is omitted or is NULL, then it equals by default to the length of str, i.e. everything from from to the end of str is returned. If to and from are equal, an empty string &#39;&#39;(empty vector) is returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_substring.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_substring.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: substring</atom:title>
  <atom:content type="html">returns a substring of a string substring returns a substring of string str. The start index is 1 based. The substring is sublen characters long. This function follows SQL 92.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sub_schedule.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Replication<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sub_schedule.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sub_schedule</atom:title>
  <atom:content type="html">add scheduled job for periodic synchronization of a subscriptionAdd scheduled job for periodically synchronizing a subscription.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_system.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_system.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: system</atom:title>
  <atom:content type="html">runs a shell command from SQL The system function will run a shell command from SQL. The shell command is executed in the server&#39;s current directory as the user that owns the database server process. This function is available to dba users only. Since this is a security risk this feature is normally disabled. It can be enabled by setting the AllowOSCalls setting in virtuoso.ini to 1.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_SYS_DB_STAT.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_SYS_DB_STAT.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: SYS_DB_STAT</atom:title>
  <atom:content type="html">gathers common statistical information about the database.The SYS_DB_STAT procedure gathers common information about the whole Virtuoso database, including attached remote tables. It traverses each table and populates the SYS_COL_STAT table with data collected. SYS_DB_STAT can be used in random mode when not all rows of the tables are used to gather statistics of the database. SYS_DB_STAT gathers the following information for each column, COL, traversed in the database:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sys_lockdown.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sys_lockdown.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sys_lockdown</atom:title>
  <atom:content type="html">Set virtuoso in lockdown state and back.You must have DBA privileges to run that function. Calling this with lock_mode = 1 causes the server not to accept any new client connections, except ones coming from localhost (127.0.0.1). This will also shut down any other listeners and terminate any possibly pending processing, rolling back all open transactions and disconnecting all clients, except ones from localhost. Calling thi with lock_mode 0 reverses the effect.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sys_stat.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sys_stat.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sys_stat</atom:title>
  <atom:content type="html">Return statistical information about the Virtuoso server.This function returns the statistic related to the requested statistic name give as a parameter to the function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sys_stat_analyze.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sys_stat_analyze.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sys_stat_analyze</atom:title>
  <atom:content type="html">Collects statistics on a table and its columns for use in SQL optimization This function collects (or updates) column statistics for the table columns. It collects minimum, maximum average and distinct values for a column and a row count for the table and inserts the data into the DB.DBA.SYS_COL_STAT table. It does not make histograms for the columns. The statistics are then used by the Optimized SQL compiler. All the cached compilations are discarded, because some of them may compile differently in the light of the new data. This function will normally consider the entire database with the exception of remote tables. Since you may be concerned about time or remote tables this operation is configurable using the optional parameters, pcnt and ignore_vdb.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_sys_stat_histogram.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_sys_stat_histogram.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: sys_stat_histogram</atom:title>
  <atom:content type="html">Collects a column value histogram for use in SQL optimization This function collects (or updates) values distribution data for a given column. It splits the sorted column values in n_buckets intervals and collects the last value of each interval. The values are then inserted into the SYS_COL_HIST table. If the table in question has not been analyzed, then it calls SYS_STAT_ANALYZE for the table.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_table_set_policy.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_table_set_policy.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: table_set_policy</atom:title>
  <atom:content type="html">Sets policy function to table.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_table_drop_policy.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_table_drop_policy.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: table_drop_policy</atom:title>
  <atom:content type="html">Drops policy function from table.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_tcpip_gethostbyname.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_tcpip_gethostbyname.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: tcpip_gethostbyname</atom:title>
  <atom:content type="html">Returns IP address by host domain nameThis calls the system function gethostbyname() and returns h_addr from the hostent structure or empty string if no hostent structure returned (host not exists).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_tcpip_gethostbyaddr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_tcpip_gethostbyaddr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: tcpip_gethostbyaddr</atom:title>
  <atom:content type="html">Returns fully qualified DNS name of the host associated with given IP addressThis calls the system function gethostbyaddr() and returns h_name from the hostent structure returned by it. If no hostent structure returned, then it returns it&#39;s argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_tmp_file_name.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_tmp_file_name.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: tmp_file_name</atom:title>
  <atom:content type="html">returns the unique file name within temporary directory of the operating system The following function is used to obtain unique name of a file, which is located in temporary directory on file system. The two optional parameters can be supplied: prefix of the file and extension for it. These will be prepended and appended (dot MUST be omitted) to the unique string. The directory where this file is located depends of $TMPDIR or %TMP% environment settings for UNIX&#39;s and Windows platforms respectively. If these environment settings are not available or empty, the defaults will be used for the operation system. (in practice for most UNIX&#39;s it&#39;s /tmp or /var/tmp directory). Note that this function do NOT open the file, it only give us a name.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_tidy_html.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_tidy_html.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: tidy_html</atom:title>
  <atom:content type="html">Invoke built-in version of HTML Tidy utility to fix typical errors in HTML text This function improves the given source HTML text, by invoking a custom version of HTML Tidy utility. To learn more about Tidy see http://www.w3.org/People/Raggett/tidy/ . Some particular combinations of errors in source HTML may cause Tidy to misinterpret the source so the output may be incomplete or corrupted. This is an unavoidable problem, due to heuristic nature of the procedure. On the other hand, Tidy will process almost any HTML suitable for some &quot;popular&quot; browser, e.g. Internet Explorer or Netscape Navigator.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_tidy_list_errors.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_tidy_list_errors.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: tidy_list_errors</atom:title>
  <atom:content type="html">Invoke built-in version of HTML Tidy utility to get list of errors in given input HTML textThis function lists errors in given source HTML text, by invoking some custom version of HTML Tidy utility. To learn more about Tidy see http://www.w3.org/People/Raggett/tidy/.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_timezone.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_timezone.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: timezone</atom:title>
  <atom:content type="html">get timezone difference from a datetimetimezone takes a datetime and returns an integer containing localtime - GMT in minutes.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_trace_off.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_trace_off.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: trace_off</atom:title>
  <atom:content type="html">Disable extra logging for Virtuoso serverYou must have DBA privileges to run that function. This function is used to disable logging of various information enabled by default with the TraceOn ini file option or with the trace_on() function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_trace_on.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Debug<atom:link href="http://docs.openlinksw.com/virtuoso/fn_trace_on.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: trace_on</atom:title>
  <atom:content type="html">Enable extra debug loggingThis function requires dba privileges. This function enables logging specified server operations for debugging purposes. The log entries will be shown at the server console (if started with foreground option) and will be written into the server message log file. The traceable events are divided into several groups: user activity, transactions, compilation of the SQL statements, DDL statements, statements execution and VDB actions.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_trace_status.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_trace_status.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: trace_status</atom:title>
  <atom:content type="html">show current trace settingsYou must have DBA privileges to run that function. This function returns an array of all available trace options and current status of the traces.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_tree_md5.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_tree_md5.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: tree_md5</atom:title>
  <atom:content type="html">returns MD5 checksum of array argumentReturns a string of 16 characters representing the binary MD5 checksum of the argument. The argument can be any array or scalar.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_hs_resolve.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Miscellaneous<atom:link href="http://docs.openlinksw.com/virtuoso/fn_hs_resolve.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: HS_Resolve</atom:title>
  <atom:content type="html">Returns URL that represents the given DOIReturns URL that represents the given DOI. The function is installed from the hslookup plugin which uses http://www.handle.net/. Note that you need to have in your Virtuoso database ini file in section Plugins added the hslookup.dll file, which location should be in the plugins folder under your Virtuoso server installation. For ex:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_acos.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Number<atom:link href="http://docs.openlinksw.com/virtuoso/fn_acos.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: trigonometric</atom:title>
  <atom:content type="html">trigonometric functions All these functions work with double precision floating point numbers. They convert their argument to an IEEE 64-bit float and return a result of that type.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_trim.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_trim.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: trim</atom:title>
  <atom:content type="html">removes characters from both ends of string argumenttrim returns a copy of subsequence of string str with all the characters present in trimchars trimmed off from the beginning. If the second argument is omitted, it is a space &#39; &#39; by default. rtrim is similar except that it trims from the right. trim trims from both ends.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_txn_error.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Transaction<atom:link href="http://docs.openlinksw.com/virtuoso/fn_txn_error.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: txn_error</atom:title>
  <atom:content type="html">poison current transaction forcing rollback Calling this function will poison the current transaction. This means that it is forced to roll back at when committed. The code can be in integer that selects the error message generated when trying to commit. This is useful before signalling application errors from SQL code that runs in manual commit mode. This can ensure that even if the client attempts a commit after getting the error signalled by the application the transaction will not commit. The code should be the constant 6, resulting the in the &#39;transaction rolled back due to previous SQL Error&#39;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_txn_killall.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Transaction<atom:link href="http://docs.openlinksw.com/virtuoso/fn_txn_killall.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: txn_killall</atom:title>
  <atom:content type="html">kill all pending transactions This function will terminate all pending transactions. This can be used for resetting infinite loops in stored procedures etc. The code determines the error reported to the client. Number 6 is preferable, corresponding to the &#39;transaction rolled back due to previous SQL error&#39;. Once any SQL statement or procedure notices that its transaction is dead, e.g. deadlocked, it signals the error and takes appropriate action, which is typically to signal the error to the caller and ultimately to the client.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_ucase.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_ucase.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: ucase</atom:title>
  <atom:content type="html">returns upper case version of string argumentucase returns a copy of string str with all the lowercase alphabetical characters converted to corresponding uppercase letters. This includes also the diacritic letters present in the ISO 8859/1 standard in range 224 - 254 decimal, excluding the character 255, y diaeresis, which is not converted to a German double-s. upper is just an alias for ucase.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_delete_binding.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_delete_binding.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_delete_binding</atom:title>
  <atom:content type="html">Causes one or more bindingTemplate structures to be deleted.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_delete_business.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_delete_business.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_delete_business</atom:title>
  <atom:content type="html">Remove one or more businessEntity structures.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_delete_service.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_delete_service.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_delete_service</atom:title>
  <atom:content type="html">Remove one or more businessService structures.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_delete_tModel.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_delete_tModel.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_delete_tModel</atom:title>
  <atom:content type="html">Remove or retire one or more tModel structures.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_discard_authToken.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_discard_authToken.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_discard_authToken</atom:title>
  <atom:content type="html">Inform a UDDI server that the authentication token can be discarded. The uddi_discard_authToken message is used to tell a UDDI-enabled server that the authentication token can be discarded. Subsequent calls that use the same authToken may be rejected. This message is optional for UDDI-enabled servers that do not manage session state or that do not support the get_authToken message.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_find_binding.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_find_binding.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_find_binding</atom:title>
  <atom:content type="html">Retrieves matching bindings The uddi_find_binding message returns a bindingDetail message that contains a bindingTemplates structure with zero or more bindingTemplate structures matching the criteria specified in the argument list.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_find_business.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_find_business.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_find_business</atom:title>
  <atom:content type="html">Retrieves a businessList message matching supplied criteria.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_find_service.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_find_service.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_find_service</atom:title>
  <atom:content type="html">Retrieves serviceList message matching search criteria</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_find_tModel.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_find_tModel.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_find_tModel</atom:title>
  <atom:content type="html">locate list of tModel entries matching supplied criteria This uddi_find_tModel message is for locating a list of tModel entries that match a set of specific criteria. The response will be a list of abbreviated information about tModels that match the criteria (tModelList).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_get_authToken.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_get_authToken.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_get_authToken</atom:title>
  <atom:content type="html">Obtain authentication token. The uddi_get_authToken message is used to obtain an authentication token. Authentication tokens are opaque values that are required for all other publisher API calls. This message is not required for UDDI-enabled servers that have an external mechanism defined for users to get an authentication token. This API is provided for implementations that do not have some other method of obtaining an authentication token or certificate, or that choose to use password-based authentication.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_get_bindingDetail.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_get_bindingDetail.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_get_bindingDetail</atom:title>
  <atom:content type="html">Request run-time bindingTemplate location information. The uddi_get_bindingDetail message requests the run-time bindingTemplate information for the purpose of invoking a registered business API.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_get_businessDetail.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_get_businessDetail.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_get_businessDetail</atom:title>
  <atom:content type="html">returns complete businessEntity information for one or more specified businessEntities</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_get_businessDetailExt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_get_businessDetailExt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_get_businessDetailExt</atom:title>
  <atom:content type="html">Returns extended businessEntity information for one or more specified businessEntities. The uddi_get_businessDetailExt message returns extended businessEntity information for one or more specified businessEntities. This message returns exactly the same information as the get_businessDetail message, but may contain additional attributes if the source is an external registry that is compatible with this API specification, rather than a UDDI-enabled server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_get_registeredInfo.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_get_registeredInfo.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_get_registeredInfo</atom:title>
  <atom:content type="html">Retrieve an abbreviated list of all businessEntity keys. The uddi_get_registeredInfo message is used to get an abbreviated list of all businessEntity keys and tModel keys controlled by the entity associated with the credentials passed.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_get_serviceDetail.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_get_serviceDetail.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_get_serviceDetail</atom:title>
  <atom:content type="html">request full information about a known businessService structure</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_get_tModelDetail.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_get_tModelDetail.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_get_tModelDetail</atom:title>
  <atom:content type="html">Request full information about a known tModel structure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_save_binding.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_save_binding.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_save_binding</atom:title>
  <atom:content type="html">save or update a complete bindingTemplate structure The uddi_save_binding message is used to save or update a complete bindingTemplate structure. This message can be used to add or update one or more bindingTemplate structures to one or more existing businessService structures.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_save_business.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_save_business.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_save_business</atom:title>
  <atom:content type="html">Save or update information about a complete businessEntity structure. The uddi_save_business message is used to save or update information about a complete businessEntity structure. This message has the broadest scope of all of the save calls in the publisher&#39;s API, and can be used to make sweeping changes to the published information for one or more businessEntity structures controlled by an identity.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_save_service.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_save_service.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_save_service</atom:title>
  <atom:content type="html">Adds or updates one or more businessService structures.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/me_uddi_save_tModel.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>UDDI<atom:link href="http://docs.openlinksw.com/virtuoso/me_uddi_save_tModel.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uddi_save_tModel</atom:title>
  <atom:content type="html">Adds or updates one or more tModel structures.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_udt_defines_field.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_udt_defines_field.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: udt_defines_field</atom:title>
  <atom:content type="html">Determines whether a user defined type contains a specified member.This function is used to determine whether the supplied member_name is a member contained by the supplied udt.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_udt_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_udt_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: udt_get</atom:title>
  <atom:content type="html">Retrieves a copy of the requested member from a user defined type instanceThis function returns a copy of the member named member_name, if any, for type instance udt_inst. It is the functional equivalent of member observer.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_udt_implements_method.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_udt_implements_method.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: udt_implements_method</atom:title>
  <atom:content type="html">provides a handle to the first method with specific name in a user defined type.This returns a non-zero value (true) if the udt has an instance method with a name equal to the value of method_name. For methods with the same name, but with different signatures this function will return the handle of the first method in order of definition. If a method is not found, 0 will be returned. The return value can be used to call the method using the indirect call statement. In which case an instance should be passed as a first argument to the indirect call statement.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_udt_instance_of.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_udt_instance_of.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: udt_instance_of</atom:title>
  <atom:content type="html">returns the type name of supplied type or compares two input types.This function returns information about the supplied type(s). There are two versions of this function, one returns the name of the type of the supplied argument, and the other than compares two supplied arguments for matching types. An error will be signalled if either of the types is not defined.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_udt_set.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_udt_set.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: udt_set</atom:title>
  <atom:content type="html">This copies the instance udt_inst, sets new_value to the member with a name equal to the value of member_name (if any) and returns the modified instance copy. This is a functional equivalent of a member mutator.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_unimport_clr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>User Defined Types &amp; The CLR<atom:link href="http://docs.openlinksw.com/virtuoso/fn_unimport_clr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: unimport_clr</atom:title>
  <atom:content type="html">This function automatically drops the SQL Type wrappers based on the CLR Reflection API.This function automatically drops the SQL Type wrappers based on the CLR Reflection API. If there is compiled Virtuoso/PL code that references the type it will fail to execute (with a compilation error) when executed or compiled.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_unimport_jar.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Type Mapping<atom:link href="http://docs.openlinksw.com/virtuoso/fn_unimport_jar.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: unimport_jar</atom:title>
  <atom:content type="html">Drops SQL wrapper types of selected Java classesThis function calls the jvm_ref_import() function to produce the XML, then transforms it to a set of DROP TYPE statements and executes them.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_updateXML.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_updateXML.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: updateXML</atom:title>
  <atom:content type="html">Create a changed copy of given document by replacing some nodes.This is a synonym name for XMLUpdate() function. This name is added for compatibility with Oracle 9i.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_upper.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>String<atom:link href="http://docs.openlinksw.com/virtuoso/fn_upper.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: upper</atom:title>
  <atom:content type="html">returns upper case version of string argumentucase returns a copy of string str with all the lowercase alphabetical characters converted to corresponding uppercase letters. This includes also the diacritic letters present in the ISO 8859/1 standard in range 224 - 254 decimal, excluding the character 255, y diaeresis, which is not converted to a German double-s. upper is just an alias for ucase.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_CHANGE_PASSWORD.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_CHANGE_PASSWORD.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_CHANGE_PASSWORD</atom:title>
  <atom:content type="html">Change the password of an existing user account.This function is used to change the password of an existing user account.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_CREATE.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_CREATE.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_CREATE</atom:title>
  <atom:content type="html">create a new user accountThis function creates a new user account. The account is valid for SQL and/or DAV, depending n options.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_DROP.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_DROP.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_DROP</atom:title>
  <atom:content type="html">This deletes a user ccount, optionally including schema objects, DAV resources and other possible resources owned by the user. This is used to remove an existing user account from local security schema.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_GET_OPTION.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_GET_OPTION.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_GET_OPTION</atom:title>
  <atom:content type="html">Retrieve a user option for a given user account.This function is used to retrieve an existing user option.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_GRANT_ROLE.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_GRANT_ROLE.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_GRANT_ROLE</atom:title>
  <atom:content type="html">Assign an existing role to an existing security object.This function is used to assign an existing role to an existing security object. This is the same as the GRANT &lt;role&gt; statement. All roles assigned to the role object will be inherited.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_REVOKE_ROLE.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_REVOKE_ROLE.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_REVOKE_ROLE</atom:title>
  <atom:content type="html">Removes a role from an existing security object.This function is used to remove a role from the specified security object. This is equivalent to using the REVOKE &lt;role&gt; statement.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_ROLE_CREATE.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_ROLE_CREATE.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_ROLE_CREATE</atom:title>
  <atom:content type="html">create a new SQL role. Same as the create role statemen.. Creates a new SQL role.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_ROLE_DROP.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_ROLE_DROP.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_ROLE_DROP</atom:title>
  <atom:content type="html">Remove an existing role (group).This is used to remove an existing role (group) from the local security schema.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_SET_QUALIFIER.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_SET_QUALIFIER.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_SET_QUALIFIER</atom:title>
  <atom:content type="html">Change the default catalog (qualifier/database) of a user account.This function is used to change the default catalog (qualifier/database) of a given user account.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_USER_SET_OPTION.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_USER_SET_OPTION.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: USER_SET_OPTION</atom:title>
  <atom:content type="html">Set a user option for a given user account.This function is used to set a User Option. The options can be any one of those described in User Options section or any other option. Note that existing option will be replaced.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_user_set_password.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_user_set_password.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: user_set_password</atom:title>
  <atom:content type="html">Allows dba to change a user&#39;s password.Explicitly sets a new password for the SQL account user_name to new_password. Only users in the dba group may execute this function. It allows the database administrator to reset lost passwords of SQL accounts. The new password will be set without further confirmation, so the DBA must be sure of the new password.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_username.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SQL<atom:link href="http://docs.openlinksw.com/virtuoso/fn_username.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: username</atom:title>
  <atom:content type="html">returns the login name of the current userReturns the login name of the user of the connection. Selecting &gt;user is equivalent.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_uudecode.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Encoding &amp; Decoding<atom:link href="http://docs.openlinksw.com/virtuoso/fn_uudecode.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uudecode</atom:title>
  <atom:content type="html">Decodes a string previously encoded by uuencode Uudecode transforms uuencoded data into original form. Uuencode may return a number of sections as a vector of them, each of these sections should be decoded by separate call and results should be concatenated in order to compose original text. The mode of decoding should match to the mode used for encoding, of course. RFC 2045, (N. Borenstein, N. Freed. MIME (Multipurpose Internet Mail Extensions) Part One: The Format of Internet Message Bodies), contains detailed description of most important encodings used by mail systems. Older RFC 1521 is now obsoleted. Currently, eight conventions are used for mail attachments. In Virtuoso, they are enumerated by integer IDs.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_uuencode.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Encoding &amp; Decoding<atom:link href="http://docs.openlinksw.com/virtuoso/fn_uuencode.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uuencode</atom:title>
  <atom:content type="html">Encodes string or string session into sequence of printable characters, suitable for transfer via &quot;ASCII-only&quot; data channels There are many protocols, like classic UNIX uuencode, which are used to transmit binary files over transmission mediums that do not support other than simple ASCII data. The epoch of physical lines of such sort is in past but file attachments in most popular mail systems still follow old regulations. Encoded data are transmitted as a sequence of one or more &quot;sections&quot;. They may be stored or sent as independent documents. Every section contains some range of original document&#39;s data. They may be decoded one after another, and original document may be composed by concatenation of decoded fragments. If the document is small (or if there&#39;s no limit on the size of message), it may be sent as single section. Every section has some header and footer and a set of lines with data between them. Headers and especially footers are usually optional and may vary from system to system whereas data lines are described by standards. Data lines of any two consequent sections may be concatenated together, if needed, to create longer section.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_uuvalidate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Mail<atom:link href="http://docs.openlinksw.com/virtuoso/fn_uuvalidate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: uuvalidate</atom:title>
  <atom:content type="html">Encodes string or string session into sequence of printable characters, suitable for transfer via &quot;ASCII-only&quot; data channels This function tries to ensure what applied data have a pointed encoding mode. If mode parameter is 0 (ie unknown) or if the validation fails, it will try to determine which mode was used in fact. RFC 1521, (N. Borenstein, N. Freed. MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies), contains detailed description of most important encodings used by mail systems. RFC 2045, (N. Borenstein, N. Freed. MIME (Multipurpose Internet Mail Extensions) Part One: The Format of Internet Message Bodies). Currently, eight conventions are used for mail attachments. In Virtuoso, they are enumerated by integer IDs.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_check.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_check.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_CHECK</atom:title>
  <atom:content type="html">Checks the package has not been altered since installationThis checks to see if the elements of the package are as they are defined in the original distribution. A list of differing elements is returned. This does not always indicate a corruption since a later version or another package may add columns to tables, and some resources may be customized after installation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_check_installability.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_check_installability.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_CHECK_INSTALLABILITY</atom:title>
  <atom:content type="html">Checks the presence and correct versions of required packages and of the Virtuoso platformChecks the presence and correct versions of required packages and of the Virtuoso platform. It does not execute any pre-install Virtuoso/PL code from the package, so there is no guarantee that installation will be successful if the check found no error.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_check_uninstallability.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_check_uninstallability.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_CHECK_UNINSTALLABILITY</atom:title>
  <atom:content type="html">Checks if the package can be uninstalled.Checks if the package can be uninstalled. It does not executes any pre-uninstall Virtuoso/PL code from the package, so there is no guarantee that uninstallation will be successful if the check found no error.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_fail_check.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_fail_check.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_FAIL_CHECK</atom:title>
  <atom:content type="html">Signals package check failuremakes &quot;rollback work&quot;, exits from atomic mode and fails server with raw_exit(-1)</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_install.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_install.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_INSTALL</atom:title>
  <atom:content type="html">Invoke VAD installation processInvoke the install operation from interactive SQL or from the web user interface. This will: If there was a failure in mid-install, such as running out of disk or some other serious unrecoverable database error, the server exits. The installation can be undone manually by halting the server, deleting the transaction log file and restarting. The server will start from the checkpoint as if the installation was never attempted.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_load_file.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_load_file.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_LOAD_FILE</atom:title>
  <atom:content type="html">executes statements of a SQL fileThis splits a plain sql file into single statements and executes them one by one. The root directory for this procedure is the &#39;code&#39; root of VAD&#39;s repository.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_pack.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_pack.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_PACK</atom:title>
  <atom:content type="html">get VAD resourceThis function gets the resource identified by the sticker_uri, which contains the vad:package root element. The URIs present there are interpreted in the context of the base_uri_of_resources and the individual resources are fetched. These are parsed to make sure that they are syntactically correct and the resources are appended to the generated package resource, which is stored into the result_uri. vad_pack() returns a human-readable log of error and warning messages, vad_pack() will signal errors if some resources or database objects will be unavailable. By convention, VAD package files have the extension &#39;.vad&#39;.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_safe_exec.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_safe_exec.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_SAFE_EXEC</atom:title>
  <atom:content type="html">execute without signalling errorsSafe way to do something without generating an exception, e.g.: when it is necessary to drop a table without insurance of it&#39;s existence.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vad_uninstall.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_vad_uninstall.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VAD_UNINSTALL</atom:title>
  <atom:content type="html">Vad package uninstallationInvokes the uninstall operation from interactive SQL or from the web user interface. This will:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vd_remote_data_source.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vd_remote_data_source.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vd_remote_data_source</atom:title>
  <atom:content type="html">prepares a remote DSN for use A remote data source is uniquely identified by its DSN, the dsn argument to this function. The connstr argument is presently ignored. The user and password are the login name and password to use when communicating with the remote data source. All Virtuoso users dealing with the remote data source will appear as this user to the remote data source. Virtuoso will make as many connections as there are concurrent users of the data source. Connections are cached by Virtuoso. The default qualifier of the user of the remote data source is usually not relevant. This function connects to the DSN in order to retrieve various meta data, which it stores locally. The DSN should be defined in the server&#39;s environment and the DSN&#39;s database should be on line.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vd_remote_proc_wrapper.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vd_remote_proc_wrapper.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vd_remote_proc_wrapper</atom:title>
  <atom:content type="html">Creating a PL wrapper for remote procedure executionThis is to create a PL stored procedure to execute a Remote Stored Procedures. It returns results as a SQL result set as well as an array(vector) depending of the &#39;make_resultset&#39; flag.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vd_remote_table.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vd_remote_table.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vd_remote_table</atom:title>
  <atom:content type="html">declares an existing table as resident on a DSN previously declared with vd_remote_data_source Declares an existing table as resident on a data source previously declared with vd_remote_data_source(). This function declares the table local_name as table remote_name on the dsn. The tables names should be full, names with qualifier and owner. The names are case sensitive and must be in the exact case where they appear in the local and remote schemas. If remote_name is NULL, the effect of a possible previous vd_remote_table is reversed. The table is thereafter treated as a local table, except in procedures and statements compiled when the remote declaration was in effect.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vd_statistics.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vd_statistics.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vd_statistics</atom:title>
  <atom:content type="html">Update VDB RPC cost statistics for given DSNThis procedure will update the RPC round-trip statistics for selected data sources.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vdd_disconnect_data_source.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vdd_disconnect_data_source.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vdd_disconnect_data_source</atom:title>
  <atom:content type="html">Disconnects a data source if no active transactions are using resources from it.You must have DBA privileges to run that function. This function disconnects all the idle opened connections to a VDB datasource. If there are active transactions server-side, using connections to that datasource, they are not closed. After they finish, this function can be called again to disconnect the new idle connections. The datasource continues to be valid and any subsequent transactions using this datasource will open a new connection to it.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vdd_measure_rpc_time.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Remote SQL Data Source<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vdd_measure_rpc_time.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vdd_measure_rpc_time</atom:title>
  <atom:content type="html">Estimate VDB RPC round-trip for a given DSN in millisecondsThis function will return the estimated number of milliseconds to perform an RPC round trip on the DSN supplied.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vector.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vector.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vector</atom:title>
  <atom:content type="html">make a vectorvector returns a new vector (one-dimensional array) constructed from the given arguments.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vector_concat.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Array Manipulation<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vector_concat.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vector_concat</atom:title>
  <atom:content type="html">concatenate vectorsvector_concat takes a variable number of vectors (heterogeneous arrays) and constructs a new vector containing copies of each (top level) element in the arguments.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vhost_define.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vhost_define.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VHOST_DEFINE</atom:title>
  <atom:content type="html">define a virtual host or virtual directoryVHOST_DEFINE is used to define virtual hosts and virtual paths on the Virtuoso HTTP server. Effectively this procedure inserts a row in table DB.DBA.HTTP_PATH Virtuoso supports both flavours of virtual hosting: IP-based and name-based.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vhost_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vhost_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VHOST_REMOVE</atom:title>
  <atom:content type="html">remove a virtual host or virtual directoryvhost_remove is used to remove virtual hosts and virtual paths on the Virtuoso HTTP server. Effectively this procedure deletes a row in the table DB.DBA.HTTP_PATH. Virtuoso supports both flavours of virtual hosting: IP-based and name-based.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_virtuoso_ini_path.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_virtuoso_ini_path.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: virtuoso_ini_path</atom:title>
  <atom:content type="html">Return full name of configuration INI fileThis function returns the complete path to the configuration INI file. It is typically used by the cfg_ functions that modify or read the contents of the INI file.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_server_root.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Administration<atom:link href="http://docs.openlinksw.com/virtuoso/fn_server_root.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: server_root</atom:title>
  <atom:content type="html">Returns server working directory.This function returns the complete physical path to server working directory.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vsp_calculate_digest.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vsp_calculate_digest.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vsp_calculate_digest</atom:title>
  <atom:content type="html">calculate on server-side a digest to perform a HTTP digest authentication The vsp_calculate_digest() function is used to calculate on server-side a digest to perform a HTTP digest authentication. When the authentication type is &#39;digest&#39; the function will return a md5 checksum based on credentials , user name and password. The checksum calculation will be made as required for HTTP Digest authentication to compare against &#39;response&#39; element of credentials. If the authentication is basic a NULL will be returned.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_batch.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_batch.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vt_batch</atom:title>
  <atom:content type="html">Returns a vt batch object. This object can be used to update a free text index by feeding document information into it using vt_batch_d_id to set the free text document ID and vt_batch_feed to feed actual words. This object may not be assigned to other variables and may only be passed as an inout parameter. The batch is applied to the index by calling the VT_BATCH_PROCESS_&lt;table&gt;_&lt;column&gt; function generated by CREATE TEXT INDEX.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_batch_d_id.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_batch_d_id.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vt_batch_d_id</atom:title>
  <atom:content type="html">Specify a document to update in a vt batch. Multiple documents may be indexed or unindexed with a single batch. In this case this function will be called for each document id, in ascending order of ID.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_batch_feed.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_batch_feed.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vt_batch_feed</atom:title>
  <atom:content type="html">Add words to a free text update batch.This function allows you to add words to a free text update batch. It can be called in sequence to feed group of documents that share a common document ID and the result is similar to the single call whose text_or_xml parameter is concatenation of documents of that group. It is even allowed to mix XML and non-XML documents by feeding an XML document and some text documents: the first document to feed may be an XML document, other documents should be only texts. If one wishes to mix XML and non-XML documents, knowledge of details of the indexing method is needed. vt_batch_feed assigns a sequence number to every word of the provided document using an internal counter. The call of vt_batch_d_id not only sets document id but also resets this counter to 0. The first element of an XML document should have number 0 so it is impossible to feed an XML document if there were other calls of vt_batch_feed after the last vt_batch_d_id. Moreover, xcontains will ignore words from text documents that were fed after the first XML document, only contains will use all data.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_batch_feed_offband.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_batch_feed_offband.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vt_batch_feed_offband</atom:title>
  <atom:content type="html">Add offband information to a free text update batch.This function allows you to add offband information to a free text update batch. This should be done by index and unindex hook functions of the free text index if and only if the index is created with both &quot;CLUSTERED WITH (...)&quot; and &quot;USING FUNCTION&quot; options and the hook function returns non-zero value, i.e. disables standard indexing of the document. This function is needed only for very unusual free text indexes.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_batch_update.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_batch_update.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VT_BATCH_UPDATE</atom:title>
  <atom:content type="html">Set batch mode update of free text indexing. This function controls the time of update of a text index. If flag is ON, changes are accumulated into a change tracking table and applied as a batch. If flag is OFF, the text index is updated in the same transaction as the indexed data itself. The change tracking table is automatically created and is named VTLOG_&lt;q&gt;_&lt;o&gt;_&lt;table&gt;, in the qualifier and owner of the indexed table, where q, o and table are the qualifier, owner and name of the table. The changes accumulated into that table can be explicitly applied to the index using the VT_INC_INDEX_&lt;q&gt;_&lt;o&gt;_&lt;table&gt; function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_create_text_index.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_create_text_index.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vt_create_text_index</atom:title>
  <atom:content type="html">Add text index to an existing table The vt_create_text_index procedure adds a text index to an existing table. There can at most be one text index per table, including super tables and subtables. The table argument is a string naming the table. The column is the name of the column to index. The id_col should be the name of a unique integer row identifier column. If null, the system will either add such a column or use an existing integer primary key if one is available. The is_xml argument, if non-0, specifies that the values of the indexed column should be checked for XML well formedness and that the XML structure should be taken into account in indexing the values. Use the CREATE TEXT INDEX statement as an alternative to the vt_create_text_index function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_drop_ftt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_drop_ftt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: VT_DROP_FTT</atom:title>
  <atom:content type="html">drop free text trigger</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_vt_is_noise.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Free Text<atom:link href="http://docs.openlinksw.com/virtuoso/fn_vt_is_noise.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: vt_is_noise</atom:title>
  <atom:content type="html">determines whether input is a noise word</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_week.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_week.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: week</atom:title>
  <atom:content type="html">get number of week from a datetimeweek takes a datetime and returns an integer containing a number representing the week of year of the datetime.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_wsdl_import_udt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Web Server &amp; Internet<atom:link href="http://docs.openlinksw.com/virtuoso/fn_wsdl_import_udt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: wsdl_import_udt</atom:title>
  <atom:content type="html">Returns a string containing a UDT definitionThis function is used to create a user defined type (UDT) definition automatically based on a WSDL file. The source WSDL is supplied via a URL. The returned definition can be saved to a file and/or executed automatically to provide instant access to the new UDT.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_wst_cli.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>SOAP<atom:link href="http://docs.openlinksw.com/virtuoso/fn_wst_cli.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: wst_cli</atom:title>
  <atom:content type="html">Request a security token from WST endpointThis function is for use with a SOAP client contacting a WS-Trust endpoint for a security token.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_dsig_template_ext.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_dsig_template_ext.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: dsig_template_ext</atom:title>
  <atom:content type="html">Generates a Digital signature template based on a XML document. The function is used to generate dynamically a digital signature template containing references to be signed.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_x509_certificate_verify.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_x509_certificate_verify.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: x509_certificate_verify</atom:title>
  <atom:content type="html">Verifies X.509 certificate This function takes a X.509 certificate and verifies it against list of CA certificates. It checks for various certificate attributes such as self signed, expiration date etc. If an error is detected it will be signalled. The certificates are passed as a strings containing X.509 certificate binary data in DER (raw) format.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_X509_certificate_serialize.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_X509_certificate_serialize.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_X509_certificate_serialize</atom:title>
  <atom:content type="html">Exports a X.509 certificate from user&#39;s repository This function is used to export X.509 from user&#39;s space.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_decrypt_soap.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_decrypt_soap.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_decrypt_soap</atom:title>
  <atom:content type="html">Decrypt and verify a SOAP message The function is used to decrypt and optionally verify signature (depends of a validate_flag parameter) of a SOAP message.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_delete_temp_keys.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_delete_temp_keys.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_delete_temp_keys</atom:title>
  <atom:content type="html">Remove the temporary keys from user&#39;s space When signing an XML document or doing the reverse work like verification etc. number of temporary keys are created in user&#39;s space. These keys at some point may not needed anymore, so they can be removed from memory.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_encrypt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_encrypt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_encrypt</atom:title>
  <atom:content type="html">Encrypt and optionally sign a SOAP message Encrypt SOAP message and optionally attach an XML signature. The keys are retrieved from the key store of the calling user account.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_get_key_algo.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_get_key_algo.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_get_key_algo</atom:title>
  <atom:content type="html">Determine XML signature algorithm of a keyThe function is used to determine signing algorithm supported by given key.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_get_key_identifier.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_get_key_identifier.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_get_key_identifier</atom:title>
  <atom:content type="html">Determine a key identifierThe function returns key identifier.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_3DES_read.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_3DES_read.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_3DES_read</atom:title>
  <atom:content type="html">Importing a triple-des key into user&#39;s repository This function is used to import a triple-des serialized key into user&#39;s repository and register it with a name supplied. Note that key will not be persisted. It is loaded in the memory only.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_3DES_create.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_3DES_create.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_3DES_create</atom:title>
  <atom:content type="html">Used to make a symmetric key.Used to make a symmetric session key for triple-des algorithm.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_3DES_rand_create.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_3DES_rand_create.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_3DES_rand_create</atom:title>
  <atom:content type="html">Used to make a temporary session key.Used to make a temporary session key.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_DSA_read.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_DSA_read.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_DSA_read</atom:title>
  <atom:content type="html">Importing a DSA key into user&#39;s repository This function is used to import a DSA serialized key into user&#39;s repository and register it with a name supplied. Note that key will not be persisted. It is loaded in the memory only.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_RSA_read.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_RSA_read.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_RSA_read</atom:title>
  <atom:content type="html">Importing a RSA key into user&#39;s repository This function is used to import an RSA serialized key into user&#39;s repository and register it with a name supplied. Note that key will not be persisted. It is loaded in the memory only.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_AES_create.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_AES_create.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_AES_create</atom:title>
  <atom:content type="html">Used to make a symmetric key.Used to make a symmetric session key for AES encryption algorithm.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_AES_rand_create.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_AES_rand_create.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_AES_rand_create</atom:title>
  <atom:content type="html">Used to make a temporary session key.Used to make a temporary session key for AES encryption.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_create_cert.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_create_cert.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_create_cert</atom:title>
  <atom:content type="html">Import a key from a certificate The function is used to import a key (usually an asymmetric key like RSA or DSA) into user&#39;s space from a certificate.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_DSA_create.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_DSA_create.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_DSA_create</atom:title>
  <atom:content type="html">Used to make asymmetric DSA key.Used to make asymmetric DSA key for digital signatures. The generated key will contain private and public keys.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_exists.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_exists.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_exists</atom:title>
  <atom:content type="html">Check if named encryption key is in the user&#39;s repositoryThe function checks if key with given name exists in the user&#39;s keys.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_inst_create.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_inst_create.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_inst_create</atom:title>
  <atom:content type="html">Key instance generation The function is used to make a key reference used in encryption functions.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_remove</atom:title>
  <atom:content type="html">This will delete a key from current user&#39;s space.This will delete a key from current user&#39;s space.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_key_serialize.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_key_serialize.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_key_serialize</atom:title>
  <atom:content type="html">Extracts a key from user&#39;s repository The function returns a string containing base64 encoded binary key data. It is used to extract symmetric or asymmetric keys. So if key is asymmetric (RSA or DSA) the second parameter designate which part to extract private or public.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_set_primary_key.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_set_primary_key.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_set_primary_key</atom:title>
  <atom:content type="html">Associate a X.509 certificate with a key This function is used to associate a key (to be used as primary) with a X.509 certificate. Usually this function is called after key import from a X.509 certificate.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_x509_ss_generate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_x509_ss_generate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_x509_ss_generate</atom:title>
  <atom:content type="html">Creates a self-signed X.509v3 certificateThis function is used to create a self-signed X.509 certificate by given private key</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_x509_generate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_x509_generate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_x509_generate</atom:title>
  <atom:content type="html">Generates a X.509v3 certificate using client&#39;s public keyThis function creates a X.509v3 certificate from a public key and sign the certificate with CA private key</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_pkcs12_export.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_pkcs12_export.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_pkcs12_export</atom:title>
  <atom:content type="html">Export of a certificate and private key into Personal Information Exchange Syntax (PKCS#12) format.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_pem_export.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_pem_export.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_pem_export</atom:title>
  <atom:content type="html">Export of a certificate and optionally private key in PEM formatThe function is used to export certificate in PEM format, optionally it can export also private key (if present)</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_SPKI_read.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_SPKI_read.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_SPKI_read</atom:title>
  <atom:content type="html">Imports a public key from simple public key infrastructure (SPKI)This function is used to read an RSA public key from SPKI content.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xenc_bn2dec.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Hashing / Cryptographic<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xenc_bn2dec.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xenc_bn2dec</atom:title>
  <atom:content type="html">Prints as a string a big number serialized as binary using base64 encoding</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xte_head.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xte_head.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xte_head</atom:title>
  <atom:content type="html">Returns the vector corresponding to a head of a XML element This function takes odd number of parameters and creates vector which corresponds to a head of a XML element. The first parameter is a tag name of the head. The remaining parameters are optional. Each even parameter is a name of an attribute, each next odd parameter is a value of this attribute. If two or more attributes have the same name, the head would have only the last pair.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xte_node.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xte_node.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xte_node</atom:title>
  <atom:content type="html">Returns the vector corresponding to a XML element This function returns the vector which corresponds to a XML element. The first parameter is a head of the element. The remaining parameters are optional. Each optional parameter either is a XML element or a string. Two or more successive strings are concatenated.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xte_node_from_nodebld.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xte_node_from_nodebld.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xte_node_from_nodebld</atom:title>
  <atom:content type="html">Returns the vector corresponding to a XML element This function replaces the first item of the second argument by the first argument and returns a vector corresponding to an XML element.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xte_nodebld_acc.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xte_nodebld_acc.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xte_nodebld_acc</atom:title>
  <atom:content type="html">Adds to the first arguments all remaining arguments The xte_nodebld_acc() function successively adds the remaining arguments to the first one. If the last items of the first argument and some following arguments are strings, they are concatenated. All successive strings are concatenated. The value of the first item is the number of the non-empty items in the returned vector. The length of the returned vector is the sum of the length of the first argument and number of the remaining arguments.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xte_nodebld_final.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xte_nodebld_final.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xte_nodebld_final</atom:title>
  <atom:content type="html">Corrects input vector By default this function reduces all last empty items from the first argument and returns it, but supplied a second argument it also replaces the first item of the first argument by the second argument, but does not commit the return.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xte_nodebld_init.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xte_nodebld_init.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xte_nodebld_init</atom:title>
  <atom:content type="html">Creates the empty vectorThis function creates the empty vector and assign it to the argument.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLAGG.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLAGG.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLAGG</atom:title>
  <atom:content type="html">Produces a forest of elements from a collection of XML values XMLAGG is aggregate function that produces a forest of XML elements from the given list of xml elements. It concatenates the values returned from one column of multiple rows, unlike XMLCONCAT, which concatenates the values returned from multiple columns in the same row. The order of element in the result of XMLAGG is defined by the order of retrieval of the source data rows. It is important to remember that the order of rows in an SQL resultset defined only if there&#39;s an explicit ORDER BY clause. Hence if the order of elements in the resulting forest is important then XMLAGG should be applied to data that comes from inner SELECT statement that has an ORDER BY clause, not e.g. from a table reference. Note that XMLAGG is actually declared as DB.DBA.XMLAGG but it is not important for plain use: for compatibility with other systems, any call of XMLAGG in any SQl statement is always replaced with the call of DB.DBA.XMLAGG, no matter which qualifier and user name are in use.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLATTRIBUTES.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLATTRIBUTES.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLATTRIBUTES</atom:title>
  <atom:content type="html">Creates a list of attributes and their values This function creates a vector that may be used only as argument of XMLELEMENT function. The vector has an even number of elements, each odd element is a name of an attribute, an even element is its value. If the attribute value is NULL, then no attribute and no value is created. If none of the attribute is created, then the function returns NULL. If string_expr is a column name, then you can omit the AS clause, and Virtuoso uses the partially escaped form of the column name as the attribute name.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLAddAttribute.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLAddAttribute.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLAddAttribute</atom:title>
  <atom:content type="html">Add an attribute to the given node of an XML tree documentThe function modifies the source document by adding an attribute to the current node of source entity. The source should be an XML tree entity, not &quot;persistent XML&quot; one, should be an element entity (not attribute, text etc.) and should not be a root entity. Parameters attr_name and attr_value can be of any types that can be casted to string. attr_name can be an attribute entity, in this case both the name and the value of attr_name attribute is used and attr_value parameter must be omitted. The mode specifies how to resolve duplicate attribute names, if an source entity already has an attribute whose name is equal to attr_name. Mode 0 is similar to &quot;insert into&quot;: the function signals an error if an attribute already exists. Mode 1 is similar to &quot;insert soft&quot;: the function do nothing if an attribute already exists and not signalling an error. Mode 2 is similar to &quot;insert replacing&quot;: the function either adds a new attribute or replacing the value of existing attribute.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLAppendChildren.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLAppendChildren.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLAppendChildren</atom:title>
  <atom:content type="html">Modify an XML document by adding new children to the given entity.The function modifies the XML document of the given source XML tree entity by adding new children to the node specified by the entity. The source entity should be XML tree entity, not &quot;persistent XML&quot; entity. The value of source can be either an element entity or a root entity; source can not be an attribute entity or a leaf entity like text or processing instruction. The values passed in parameters insertion1... insertionN will be converted into XML nodes according to rules described in section Composing Document Fragments From DOM Function Arguments. After calling the function, parameter source is still a valid XML entity that points to the modified node. The value passed as source can be used in the rest of caller procedure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLCONCAT.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLCONCAT.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLCONCAT</atom:title>
  <atom:content type="html">Creates a forest of elements by concatenating a list of XML values XMLCONCAT accepts a list of XML value expressions as its arguments, and produces a forest of elements by concatenating the XML values that are returned from the same row to make one value. XMLCONCAT works like XMLFOREST, except that XMLCONCAT parameters is a list of XML elements. Null expressions are dropped from the result. If all the value expressions are null, then the function returns NULL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLELEMENT.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLELEMENT.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLELEMENT</atom:title>
  <atom:content type="html">Creates XML element XMLELEMENT takes an element name for identifier, an optional collection of attributes for the element, and arguments that make up the element&#39;s content. It returns a XML element. The second parameter may be omitted and at that time the rest parameters may be present. If one of the arguments is a call of the xpath_eval returning an attribute value, then this value would be added to element&#39;s content (not to element&#39;s attributes).</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLFOREST.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLFOREST.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLFOREST</atom:title>
  <atom:content type="html">Produces a forest of XML elements XMLFOREST produces a forest of XML elements from the given list of arguments. The arguments may be string expressions with optional aliases. If string expression is a column name, then you can omit the AS clause, and Virtuoso uses the partially escaped form of the column name as the name of the enclosing tag. If the expression evaluates to NULL, then no element is created for that expression. If none of the element is created, then the function returns NULL.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLInsertAfter.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLInsertAfter.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLInsertAfter</atom:title>
  <atom:content type="html">Modify an XML document by inserting new children after the node specified by given entity.The function modifies the XML document of the given source XML tree entity by adding new siblings to the node specified by the entity. Siblings will be added right after the node. The source entity should be XML tree entity, not &quot;persistent XML&quot; entity. The value of source should be a node entity; source can not be an attribute entity or a root entity. The values passed in parameters insertion1... insertionN will be converted into XML nodes according to rules described in section Composing Document Fragments From DOM Function Arguments. After calling the function, parameter source is still a valid XML entity that points to the same node. The value passed as source can be used in the rest of caller procedure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLInsertBefore.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLInsertBefore.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLInsertBefore</atom:title>
  <atom:content type="html">Modify an XML document by inserting new children before the node specified by given entity.The function modifies the XML document of the given source XML tree entity by adding new siblings to the node specified by the entity. Siblings will be added right before the node. The source entity should be XML tree entity, not &quot;persistent XML&quot; entity. The value of source should be a node entity; source can not be an attribute entity or a root entity. The values passed in parameters insertion1... insertionN will be converted into XML nodes according to rules described in section Composing Document Fragments From DOM Function Arguments. After calling the function, parameter source is still a valid XML entity that points to the same node. The value passed as source can be used in the rest of caller procedure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLReplace.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLReplace.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLReplace</atom:title>
  <atom:content type="html">Modify a given XML document by replacing some nodes.The function takes of the XML document referenced by source XML tree entity and modifies it by replacing nodes specified by location1, location2, ..., locationN with values specified by replacement1, replacement2, ...,replacementN. At the end of function call, the source points to the root of a modified entity. The source parameter should be an XML tree entity whose document is not locked (see Changing XML Entities in DOM Style for details). Every replacementI may be an XML tree entity, a NULL or a value of some other type that will be converted to varchar before use.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_auto.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_auto.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_auto</atom:title>
  <atom:content type="html">prepares and executes given SQL for XML string output This function prepares and executes the given SQL string, which should be a query expression with the FOR XML clause at the end of the last term. The query is passed the parameters from the params vector, which should have one element for each ? in the query text, values assigned from left to right. Consider the query: select a, b from table where a = ? and b = ?; then the params vector could reasonably be: vector(1, &#39;myfilter&#39;). The result set is converted to XML and appended to the string_output. If the string_output is omitted and the function executes in the context of a VSP page, the output is sent to the stream going to the user agent.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_auto_dtd.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_auto_dtd.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_auto_dtd</atom:title>
  <atom:content type="html">returns an XML DTD for the result of a SQL query with a FOR XML clause This function returns an XML DTD for the results of a SQL query with a FOR XML clause. The returned DTD will apply to the output generated by xml_auto with the query in question after wrapping it into the specified root element.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_auto_schema.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_auto_schema.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_auto_schema</atom:title>
  <atom:content type="html">returns an XML schema for the result of an SQL query with a FOR XML clause This function returns an XML schema for the results of an SQL query with a FOR XML clause. The returned schema will apply to the output generated by xml_auto() with the query in question after wrapping it in the specified root element.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_create_tables_from_mapping_schema_decl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_create_tables_from_mapping_schema_decl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_create_tables_from_mapping_schema_decl</atom:title>
  <atom:content type="html">returns a vector containing strings. Each string is a command to drop a table or a foreign key or to create table. xml_create_tables_from_mapping_schema_decl takes a file containing mapping schema and returns a vector containing strings. Each string is a command to drop a table or a foreign key or to create table. All tables and fields are mentioned in the mapping schema. If a field type is not defined in the mapping schema, the VARCHAR type is used.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_cut.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_cut.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_cut</atom:title>
  <atom:content type="html">creates a new XML document which contains a copy of data pointed by given XML tree- or XPER- entity In some special cases, some part of XML document, being pointed by a XML entity, should be copied into a new separate document with new entity pointing to the top-level element or the root of this document. One reason for doing this is optimization of XPER processing (see xper_cut). Another way to use this functionality is passing of some XML entity to a function, when function uses XPath operations with references to the &quot;document&#39;s root&quot;. The current node of the resulting entity is the node that is a copy of the current node of the source entity. In common, the top-level node of the copied subtree becomes the current node of the result. There are two special cases, however. If the source entity is an attribute entity, then the result is also an attribute entity and the attribute name remains the same. If the source entity points to the root of the document, the resulting entity also points to the root of the copied document, not to its top-level node. With XPER entity given, xml_cut() works exactly as xper_cut().</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_doc_output_option.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_doc_output_option.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_doc_output_option</atom:title>
  <atom:content type="html">This function reads or updates the specified XSLT output option value of the given xml_entity. The function updates the option if parameter option_value is provided, otherwise it returns the current value of the option without any side effects. Supported options are &#39;method&#39;, &#39;version&#39;, &#39;encoding&#39;, &#39;omit-xml-declaration&#39;, &#39;standalone&#39;, &#39;doctype-public&#39;, &#39;doctype-system&#39;, &#39;indent&#39; and &#39;media-type&#39;, but do not support&#39;cdata-section-elements&#39;. When the entity is serialized, the effect is very similar to the effect of the same option specified in xsl:output element of an XSLT that created the entity.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_load_schema_decl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_load_schema_decl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_load_schema_decl</atom:title>
  <atom:content type="html">returns a string with list of errors detected by XML Schema processor on reading given XML Schema definition document.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_load_mapping_schema_decl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_load_mapping_schema_decl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_load_mapping_schema_decl</atom:title>
  <atom:content type="html">creates a xml view from mapping schema. xml_load_mapping_schema_decl takes a file containing mapping schema and creates a xml view.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_namespace_scope.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_namespace_scope.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_namespace_scope</atom:title>
  <atom:content type="html">Returns a vector of all namespace declarations in all ancestors of the given XML entity.The function returns a vector of even length that consists of all declared namespace prefixes and namespace URIs from the ent and all its ancestors. This information is needed for processing XML documents that contains a mix of data and XPath expressions, such as BPEL documents.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_add_system_path.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_add_system_path.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_add_system_path</atom:title>
  <atom:content type="html">Adds path to the internal list of system paths. When validating XML parser tries to resolve system entities it searches in http_root directory. If it fails parser iterates internal list of system paths and tries to find required files there. The function adds new path in this list. List of system paths contains one directory item by default - &quot;file://system/&quot;. NOTE: List of system paths is not persistent. It means that you must add desired path each time when server starts. An ideal place for this operation in &quot;autoexec.isql&quot; file.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_get_system_paths.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_get_system_paths.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_get_system_paths</atom:title>
  <atom:content type="html">Returns vector of all system paths.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_persistent.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_persistent.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_persistent</atom:title>
  <atom:content type="html">returns an entity object (&#39;XPER entity&#39;) created from given XML document This parses the argument, which is expected to be a well formed XML fragment and returns a parse tree as a special object with underlying disk structure, named &quot;persistent XML&quot; or &quot;XPER&quot; While the result of xml_tree() is a memory-resident array of vectors, the XPER object consumes only a little amount of memory, and almost all data is disk-resident. This function is equivalent to xper_doc, and the only difference is in the order of arguments; xper_doc() has the same order of arguments as xml_tree.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_template.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_template.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_template</atom:title>
  <atom:content type="html">Execute XML template from Virtuoso PLThe xml_template() function was introduced to enable PL programming to make use of XML templates. This function expects an XML entity for the first argument, that will be the XML template file contents. Usually this entity is composed making use of the xtree_doc() function from the XML template file. The second argument should be a vector of name-value pairs of the parameters for XML template. The last argument is an output string stream for the result. If the output stream is not specified the HTTP internal stream will be used if it is available, otherwise an error will be signalled.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_tree.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_tree.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_tree</atom:title>
  <atom:content type="html">Parses an XML fragment and returns the parse tree as nested vectors.This parses the argument, which is expected to be a well formed XML fragment and returns a parse tree as a structure of nested heterogeneous vectors.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_tree_doc.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_tree_doc.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_tree_doc</atom:title>
  <atom:content type="html">returns an entity object given a tree from xml_tree This returns an entity object given a tree of the form returned by xml_tree. If it is given a string as an argument, it will automatically generate the parse tree and use it to make the entity instead requiring you to run the string through xml_tree first. Note that it is better to use xtree_doc or xper_doc for converting source XML text directly to an XML entity. If the argument is an XML tree entity, the function will return it as is, so e.g. redundant calls of xml_tree_doc will have no effect. The only thing xml_tree_doc can alter in the returned value is base URI of the document entity: if base_uri is provided and is not NULL, and argument entity has no base URI set then the provided URI is assigned to the returned entity.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_tree_doc_media_type.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_tree_doc_media_type.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_tree_doc_media_type</atom:title>
  <atom:content type="html">This function returns the media type in effect for the result of the xslt() (XSL-T) transformation , based on xsl:output &quot;media-type&quot; and &quot;method&quot; attributes of the XSL-T style-sheet applied. It accepts an entity (potentially resulting from using xslt()) as a argument and will return a string containing the media-type.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_uri_get.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_uri_get.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_uri_get</atom:title>
  <atom:content type="html">Retrieve a resource based on a URI This function combines a base URI and a relative URI and returns the referenced resource. The supported protocol identifiers are http: file: and virt:. The virt: allows referencing data stored in local Virtuoso tables without passing through HTTP. See &#39;Entity References in Stored XML&#39; for details. The effective URI will be the reference if the URI of the reference is absolute. Otherwise it will be the base URI modified by the relative reference.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_validate_dtd.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_validate_dtd.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_validate_dtd</atom:title>
  <atom:content type="html">returns a string with list of errors detected by DTD validator on reading given XML document This parses the argument, which is expected to be an XML fragment (possibly with syntax errors, violations of validity conditions etc.) and returns a human-readable list of errors as a string. DTD validation may be performed during any reading of XML source in functions xml_tree(), xml_persistent() or xper_doc(), so that an application may check XML source on the fly; severe constraint violations in source XML will be signalled as SQL runtime errors.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_validate_schema.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_validate_schema.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_validate_schema</atom:title>
  <atom:content type="html">returns a string with list of errors detected by DTD and XML Schema validator on reading given XML document. This parses the argument, which is expected to be an XML fragment (possibly with syntax errors, violations of validity conditions etc.) and returns a human-readable list of errors as a string. If there is a &quot;schemaLocation&quot; attribute in root element, XML Schema declaration will be loaded and partial schema validation will be performed. If this attribute does not exist and the Validation option below is not set to DISABLED, then an error will be returned: (&#39;FATAL : Schema declaration is not loaded&#39;). The XML Schema validation routines are tightly coupled with DTD validator. If the document contains both Schema and DTD information then both validations are made in the same time in order to provide as accurate diagnostics as possible. However, it is impossible to check whether the declared DTD matches or contradicts to the declared Schema, so the parser performs two independent validations to every item of source data. E.g. if DTD contradicts to the schema in description of some particular element and data in the document does not contain this element then no errors is reported; but if sun an element occurs in the document then either DTD validator or Schema validator will log an error.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_view_dtd.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_view_dtd.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_view_dtd</atom:title>
  <atom:content type="html">returns an XML DTD for the output of given XML VIEW This function will return an XML DTD for the output of a given XML VIEW. The returned DTD will be valid if the HTTP_... output of the view is wrapped into the specified root element.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_set_ns_decl.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_set_ns_decl.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_set_ns_decl</atom:title>
  <atom:content type="html">Registers the XML NS prefix as persistent or keeps it in properties of client connection depending on the persistance bits input value.Registers the XML NS prefix as persistent or keeps it in properties of client connection depending on the persistance bits input value.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xml_view_schema.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xml_view_schema.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xml_view_schema</atom:title>
  <atom:content type="html">returns an XML schema for the output of given XML VIEW This function return an XML schema for the output of given XML VIEW. The returned schema will be valid if the HTTP_... output of view wrapped into the specified root element.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xmlsql_update.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xmlsql_update.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xmlsql_update</atom:title>
  <atom:content type="html">Performs insert/update/delete operations based on an XML updategram.xmlsql_update() supports XML-based insert, update, and delete operations performed on an existing table in the database. See Updategrams basics in the &quot;Web and XML section&quot; for a detailed explanation.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLUpdate.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLUpdate.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLUpdate</atom:title>
  <atom:content type="html">Create a changed copy of given document by replacing some nodes.The function takes of the XML document referenced by source XML tree entity, makes a copy of that document; then it modifies the copy by finding fragments that are values of path1, path2, ..., pathN XPATH expressions and replacing them with values specified by replacement1, replacement2, ...,replacementN; the modified copy is returned as the result of the function call. Every pathI should be a string that is a correct XPATH expression. Every such expression is evaluated according to the rules for XPATH expressions in XSLT (attribute entities are not cast to their string values). The context node is source, context size and position are both equal to 1. Every replacementI may be an XML tree entity, a NULL or a value of some other type that will be converted to varchar before use.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xpath_eval.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xpath_eval.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xpath_eval</atom:title>
  <atom:content type="html">Applies an XPATH expression to a context node and returns result(s). This function returns the result of applying the XPath expression to the context node. By default only the first result is returned, but supplying a third argument allows you to specify an index for the value; the default assumes a value of 1 here. A value of 0 returns an array of 0 or more elements, one for each value selected by the XPath expression. When this function returns an entity in a result set, the client will see an nvarchar value containing the serialization of the entity, complete with markup. When the entity is passed as an SQL value it remains an entity referencing the node of a parsed XML tree, permitting navigation inside the tree. The expression can be passed parameters by specifying a fourth argument to xpath_eval(). This will be a vector of name/value pairs. The values can be referenced from inside XPath expression by using their names with &#39;$&#39; prefix. You may use any Virtuoso data type. The names in the parameter vector should appear without the &#39;$&#39; sign. If any of the parameter values is NULL the parameter will be ignored because NULL has no XPath counterpart. If the same name appears more than once in the vector, the last name/value pair is used and all preceding pairs with this name are silently ignored. Obviously, names should be strings that are valid XPath variable names.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xper_cut.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xper_cut.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xper_cut</atom:title>
  <atom:content type="html">creates a new &quot;persistent XML&quot;document which contains a copy of data pointed by given XPER entity As noted in the Storage in Database section, a subtree may be extracted from a document during writing of &quot;persistent XML&quot; entity into field of type LONG VARCHAR. The procedure of converting a subtree into complete document is known as &quot;cutting&quot;. Cutting is performed only for &quot;persistent XML&quot; documents, it has nothing common with serialization of XML entities in form of plain XML text. Usually it is the job of the Server itself who decides whether a cutting operation should be performed or not, without any specific activity at application level. The CPU time occupied due to cutting is up to 10 times greater than the CPU time of plain copying of LONG VARCHAR, but the amount of disk I/O is about the same, so the optimization rules discussed below are important only for time-critical, memory-located database applications. The Virtuoso Server tries to reduce the number of cuttings to an absolute minimum. First of all, cutting is not performed when a given XML entity refers to the root of the document, or to the only child of the root, because the result of such cutting will be identical to original document. In addition, every document remembers the result of last cutting performed on data from this document, so if data of some XML entity are saved in many places without saving of other XML entities between them, cutting will be done only once and plain copying will be done for every subsequent saving.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xper_doc.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xper_doc.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xper_doc</atom:title>
  <atom:content type="html">returns an entity object (&#39;XPER entity&#39;) created from an XML document This parses the argument, which is expected to be a well formed XML fragment and returns a parse tree as a special object with underlying disk structure, named &quot;persistent XML&quot; or &quot;XPER&quot; While the result of xml_tree is a memory-resident array of vectors, the XPER object consumes only a little amount of memory, and almost all data are disk-resident. XPERs are better then &quot;XML trees&quot; for large documents and for &quot;write once -- read many&quot; stores such as a table with one XML document per row used as a &quot;library&quot; of documents. To be saved in a LONG VARCHAR column, &quot;XML tree&quot; entity will be converted back to plain text of XML syntax; but &quot;XPER&quot; entity will be saved as a ready-to-use disk structure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xper_locate_words.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xper_locate_words.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xper_locate_words</atom:title>
  <atom:content type="html">returns a smallest fragment of persistent XML entity object (&#39;XPER entity&#39;) such that it contains some range of words in its textThis receives the XML entity and returns its fragment or signals an error.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xper_right_sibling.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xper_right_sibling.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XPER navigation</atom:title>
  <atom:content type="html">low-level navigation functions for persistent XMLs, useful for import of huge amounts of XML data All these functions work with &quot;persistent XML&quot; (XPER) entities only, signalling errors if given entity points to &quot;XML tree&quot;. They are useful when applications need to read a huge XML document, especially something like a datasheet dump or event log with a large number of uniform records, and is required to process all records of the document, e.g. import them into the database. Consider a real sample of import all data from ODP&#39;s content.xml dump which contains more than 2,000,000 descriptions of various Web-sites, and the length of the file is more than 600Mb. The file has root element named &#39;RDF&#39; and all descriptions are their children named either &#39;Topic&#39; or &#39;ExternalPage&#39;. This code looks suitable for importing these children: It looks fine and it passes small tests but it will not work on real data!</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xpf_extension.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xpf_extension.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xpf_extension</atom:title>
  <atom:content type="html">declare an XPath extension function This function is used to declare a new XPath extension function or redefine an existing function. It can be used in XPath queries and XSLT stylesheets. You should use QNames for extension functions. Note that the standard XPath functions cannot be redefined. xpf_extension() stores the functions into the SYS_XPF_EXTENSIONS system table. The input parameters will be retrieved as a strings and then will be converted to the datatype of the corresponding argument of the stored procedure.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xpf_extension_remove.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xpf_extension_remove.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xpf_extension_remove</atom:title>
  <atom:content type="html">discards an XPath extension functionRemoves a user-defined XPath function.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xquery_eval.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xquery_eval.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xquery_eval</atom:title>
  <atom:content type="html">Applies an XQUERY expression to a context node and returns result(s). The xquery_eval function returns the result of applying the xquery expression to the context node. By default only the first result is returned, but supplying a third argument allows you to specify an index for the value, the default assumes a value of 1 here. A value of 0 returns an array of 0 or more elements, one for each value calculated by the xquery expression. When an entity is returned in a result set to a client the client will see an nvarchar value containing the serialization of the entity, complete with markup. When the entity is passed as a SQL value it remains an entity referencing the node of a parsed XML tree, permitting navigation inside the tree. The expression can be passed parameters by specifying a fourth argument to xquery_eval(). This will be a vector of name/value pairs. The values can be referenced from inside XPath expression by using their names with &#39;$&#39; prefix. You may use any Virtuoso data type. The names in the parameter vector should appear without the &#39;$&#39; sign. If any of the parameter values is NULL the parameter will be ignored because NULL has no XPath counterpart. If the same name appears more than once in the vector, the last name/value pair is used and all preceding pairs with this name are silently ignored. Obviously, names should be strings that are valid XQuery variable names.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xslt.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xslt.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xslt</atom:title>
  <atom:content type="html">returns an XML document transformed by an XSLT stylesheet This function takes the URI of a stylesheet and an XML entity and produces an XML entity representing the transformation result of the given entity with the given stylesheet. The result tree is separate from the argument tree and the only reference to it is the returned entity. Errors occurring in the transformation will be signalled as SQL states, with XML or XSLT specific conditions beginning with XS or XP. The stylesheet can be passed parameters by specifying a third argument to xslt(). This will be a vector of name/value pairs. The values can be referenced from inside XPath expressions in the stylesheet. You may use any Virtuoso data type. The names in the parameter vector should appear without the &#39;$&#39; sign. If any of the parameter values is NULL the parameter will be ignored because NULL has no XPath counterpart. If the same name appears more than once in the vector, the last name/value pair is used and all preceding pairs with this name are silently ignored. Obviously, names should be strings that are valid XPath variable names. xslt() applies the transformation in the sheet to the specified entity. The result is the root element of the result tree, an XML entity. This entity can be used as input to another transformation, can be serialized and sent to an HTTP client or stored, etc.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xslt_format_number.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xslt_format_number.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xslt_format_number</atom:title>
  <atom:content type="html">returns formatted string representation of a numeric valuexslt_format_number is an function wrapper for the format-number() XSLT function. It always uses the default formatting parameters described in the XSLT standard.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xslt_sheet.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xslt_sheet.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xslt_sheet</atom:title>
  <atom:content type="html">declares an XSL stylesheet for use This function takes a name and the root element of a parsed XML document and defines these as a stylesheet. The unique element child of the entity object&#39;s document should be an xsl:stylesheet element. Included or imported stylesheets will be located relative to the base URI of the entity passed to xslt_sheet(). Once a stylesheet thus defined it can be used as the stylesheet argument of xslt.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xslt_stale.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xslt_stale.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xslt_stale</atom:title>
  <atom:content type="html">force reload of XSL stylesheet This function can be used to force Virtuoso to reload a cached stylesheet from the URI when next used with xslt() or http_xslt(). Using this function before every application of the stylesheet is extremely inefficient. If stylesheets are stored in the database, you can use this function in an update trigger on the table storing the stylesheets but you don&#39;t have to use it before every application of the sheet. This function never needs to be applied to a stylesheet URI with the file:// protocol since xslt() and http_xslt() will automatically detect a stale cache entry. However if the stylesheet is stored on a remote web server, or if the stylesheet contains subdocuments ( e.g. external XML entities, xsl:include or xsl:import statements) this function is needed to force a reload.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xtree_doc.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_xtree_doc.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xtree_doc</atom:title>
  <atom:content type="html">returns an entity object created from an XML document This parses the argument, which is expected to be a well formed XML fragment and returns a parse tree as a special memory-resident object. While xper_doc creates some disk-resident data structure, xtree_doc() will work faster but it may require more memory. You may wish to use xtree_doc for small documents (e.g. less than 5 megabytes and xper_doc for larger documents.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.registerUser.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.registerUser.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xmlStorageSystem.registerUser</atom:title>
  <atom:content type="html">Register a user with the XML Storage SystemThis method allows users to register within XML Storage System. The actions performed on the server are:</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.mailPasswordToUser.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.mailPasswordToUser.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xmlStorageSystem.mailPasswordToUser</atom:title>
  <atom:content type="html">Mail password to user.This method is used to send the password for user identified by email. To work properly the default SMTP server Virtuoso INI file setting must be set properly.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.getServerCapabilities.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.getServerCapabilities.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xmlStorageSystem.getServerCapabilities</atom:title>
  <atom:content type="html">Retrieve server specific information.This method is used to obtain information about the capabilities of the server, such as files size limitations, supported types, etc...</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.deleteMultipleFiles.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.deleteMultipleFiles.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xmlStorageSystem.deleteMultipleFiles</atom:title>
  <atom:content type="html">Remove files from XML Storage System DirectoryThis method is used for removing files from the repository.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.saveMultipleFiles.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>
  <atom:link href="http://docs.openlinksw.com/virtuoso/fn_xmlStorageSystem.saveMultipleFiles.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: xmlStorageSystem.saveMultipleFiles</atom:title>
  <atom:content type="html">Upload a set of files to XML Storage System directory.This method allows users to upload a set of files. The files will be stored in WebDAV repository and will be accessible via HTTP.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/fn_XMLType.XMLType.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>XML<atom:link href="http://docs.openlinksw.com/virtuoso/fn_XMLType.XMLType.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-16T14:26:59Z</atom:published>
  <atom:title>Function: XMLType.XMLType</atom:title>
  <atom:content type="html">The method creates an XMLType instance from src XML entity. If parameter src is not an XML entity then it is converted to it via internal call of