HI Alex,

The procedures can be used to dump one or many graphs and are typically used 
for dumping and reloading all the graphs the a Virtuoso Quad Store and reload 
into another Virtuoso or other store as it is dumped as to standard TTL format. 
 To uses as described  you would simply load the procedures provided into 
Virtuoso using isql from command line or even via the Conductor and use the 
“dump_graph()” and “load_graph()” function to dump and load graphs accordingly 
...

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.      //              http://www.openlinksw.com/
10 Burlington Mall Road, Suite 265, Burlington MA 01803
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers

On 3 Jun 2012, at 12:11, Alex wrote:

> Hello there,
> just a quick question. In order to export a graph, do I have to create the 
> procedures described here: 
> http://www.openlinksw.com/dataspace/dav/wiki/Main/VirtDumpLoadRdfGraphs
> 
> If yes could someone help how to do this? Do I Just create a script file with 
> the code and load it via isql?
> 
> Is there any other method for exporting a graph such as an internal procedure?
> 
> Thanks.
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> Virtuoso-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to