As the original error message I posted implies I am attempting to use the
function via SPARQL hence the bif: prefix and why the error comes from the
SPARQL compiler
OpenLink.Data.Virtuoso.VirtuosoException : Virtuoso Error: SQL_ERRORSQLSTATE:
37000Message: [Virtuoso .NET Data
Hi Hugh,
I can't find the exact version right now, but it's indeed a quite recent
Virtuoso 7 single server (open source version). Is there a way to find
the build from the command line? Also, is it possible that slightly
different builds use the database files in a different way, thus causing
Hi Nicola,
You can run the command
virtuoso-t -?
to get the full version and build date ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn --
Hi Hugh,
in the meanwhile I found that the build has SHA
48f0ef879b913c5d3b306c1f83390079c5416fe6.
Nicola
Il 07/02/2014 12:26, Hugh Williams ha scritto:
Hi Nicola,
You can run the command
virtuoso-t -?
to get the full version and build date ...
Best Regards
Hugh Williams
On 2/5/14 5:56 PM, Kevin wrote:
Kingsley,
I would like to make some final clarifications before I begin. This
is a big time consuming decision so I want to try to choose wisely.
-Should I transform only the portion of my database (half) that is
going to need provenance reification?
Hi Rob,
Ah, it must be a bif: (built-in-function) vs sql: (Virtuoso PL) function change
then as there were some changes for SPARQL 1.1 compliance in this area in 2012,
so use the sql: prefix instead:
SQL sparql delete from http://sample/ {
`bif:rdf_make_iid_of_qname('http://localhost:8890')`
Virtuoso Fans,
For a year I have really needed Virtuoso to provide a unique integer ID for
each RDF triple. In other words, I would like Virtuoso to store SPOGI (Like
AllegroGraph) instead of just SPOG. Often people question if I really need the
index. It is essentially for numerous reasons
Hi Everybody,
I have a problem with the SPARQL engine of Virtuoso. I want to use it
with the next ontology:
?xml version=1.0?
rdf:RDF
xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#;
xmlns:owl=http://www.w3.org/2002/07/owl#;
xmlns:xsd=http://www.w3.org/2001/XMLSchema#;
Hi,
I try to delete a larger graph (300M triples) on my VOS7 store
(07.00.3203-pthreads for Linux, Database version 3126) but VOS crashes
on a memory problem.
I down scaled memory assignment in virtuoso.ini to 12GB (the box has 16
GB, previously 14 GB was assigned) in virtuoso.ini
; 12 GB
On 2/4/14 6:46 AM, Nádudvari Gyuri (Reedcourty) wrote:
Hi Everybody,
I have a problem with the SPARQL engine of Virtuoso. I want to use it
with the next ontology:
?xml version=1.0?
rdf:RDF
xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#;
Hi Rob,
The change was made between the 6.1.5 and 6.16 release it seems, but testing
against an older 6.1.3 build either the bif or sql: prefixes work, so you
could change to use the latter to cover all bases:
C:\virtuoso-opensource-win64-20110330\virtuoso-opensource\database..\bin\virtuoso-t
Ok thanks
Could you perhaps track down when exactly the change happened (I.e which
release)?
Ideally my code needs to continue to be backwards compatible with people using
older Virtuoso installations so being able to detect which form of the function
call I should use by inspecting the
Hi Roland,
Did run have the log_enable(3) option to turn off transactions when performing
such large operations on graphs to reduce the memory required, as detailed in
the document at:
http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtTipsAndTricksGuideDeleteLargeGraphs
Hi Hugh,
I didn't turn of transactions by log_enable(3). I have a new try running
right now. I'll let you know if that made difference.
The VOS7 version used is:
Virtuoso Open Source Edition (Column Store) (multi threaded)
Version 7.0.0.3203-pthreads as of Sep 16 2013
Compiled for Linux
Hi Roland,
Glad to here log_enable(3) enabled the large graph to be deleted ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn --
15 matches
Mail list logo
