Hi Hugh,
Thanks for your reply. Now that we have some more constants, we can
focus on our side of things and stop trying to second guess Virtuoso.
We realized that something might be wrong with our data ( see snip
below ). Now, how did this happen? I have no idea. But we will soon ;)
I have noti
Hi Kjetil,
Just a relevant update on this topic, as Ubuntu Jaunty was released
a few days
ago, there is a new release schedule for Ubuntu out:
https://wiki.ubuntu.com/KarmicReleaseSchedule
Note that the DebianImportFreeze is set to 25th of June, so to
ensure that
Virtuoso is in the next v
Hi Hugh,1) I checked VirtuosoTest.java again. Test 1 passes only if the graph "http://demo.openlinksw.com/demo#this" is already in the DB. I oversaw this in my last run. Is this maybe intended? Test 4 passes in the first run, but fails when re-running the tests (the tupleQuery in test 4 returns 1 r
Patrick,
Just a relevant update on this topic, as Ubuntu Jaunty was released a few days
ago, there is a new release schedule for Ubuntu out:
https://wiki.ubuntu.com/KarmicReleaseSchedule
Note that the DebianImportFreeze is set to 25th of June, so to ensure that
Virtuoso is in the next version o
Oh sorry, Hugh ... now I messed my build paths completely. With the
latest sesame version (2.2.4) all tests pass. Ok. But still, my
initial problem remains. I will send you a test program later...
Best, Mirko
Am 27.04.2009 um 13:55 schrieb Mirko:
Hi Hugh,
obviously I didn't have the most
Hi Hugh,
obviously I didn't have the most recent jdbc-driver and sesame-
provider. I just downloaded the recent versions. Now, only tests 1 and
4 fail. Again, when re-running the test (i.e. running the test with an
existing context graph in the db) test 1 passes.
Driver output is:
OpenLink
Hi Daniel,
It does seem strange that your "sparql load ..." load queries report
they have successfully completed when the data has not actually
loaded completely. Typically with large datasets of this nature we
would expect an error of the form "[Virtuoso Server]SR325:
Transaction aborted
Hi Aldo,
Their are no real differences under the "hood" particularly between
iSQL and JDBC with both should be firing exactly the same query
against Virtuoso. The only difference I can think of with the SPARQL
endpoint is that queries get executed as the special "SPARQL" user.
Having said
BTW, I am not specifying any default graph when querying via /sparql.
On a related note, I assume that there are policy functions at work in
some parts of the ODS system ( attached to tables in different
modules, below the RDF views ). Is there a way to:
* List all these functions?
* Override all?