ntime exception to abort the current transaction.
You can download the maven project at
http://www.bertails.org/virtuoso/virtuoso-test.tar.gz
Regards,
Alexandre Bertails.
Hi all,
we have some issues with transactions in Virtuoso and Jena driver (or JDBC one).
Here is a typical use case for us :
1) open transaction
2) insert data into one named graph
3) insert data into another named graph
4) commit changes
Of course, in case of error, we need a global rollback.
Hi,
today we have tested the same queries in Virtuoso 5.0.11 on Linux
2.6.24 (we didn't succeed the compilation on Solaris 5.10).
As you can see on the attachment, we still have the same problem.
Alexandre.
2009/4/30 Patrick van Kleef :
> HI Alexandre,
>
>>
>> we have an "out of memory" error o
> I will have someone look at your queries, however have you already tried
> the latest vos 5.0.11 release to see if this leak has already been resolved?
>
We have considered to update to VOS 5.0.11 to potentially solve the problem
but setting up a complete environment (to compile vos, to update j
rball with :
* a simple virtuoso.ini
* RDF files and scripts to load : "scripts" directory
* scripts used to send the queries : query.sh and start.sh
* log file and report : stat.txt and report.pdf
Does anybody know if one of our queries is bad ?
Alexandre Bertails.
virtuos
Ok, actually it works, but only if the query is not already in cache.
Is there a way to log also cached queries ?
Alexandre.
2009/4/24 Alexandre Bertails
> Hi all,
>
> I also need to log SPARQL queries into Virtuoso.
>
> I have activated everything with :
>
> SQL> trac
Hi all,
I also need to log SPARQL queries into Virtuoso.
I have activated everything with :
SQL> trace_status();
and with the trace_status_show() procedure, here is what I have :
SQL> trace_status_show();
opt status
VARCHAR VARCHAR
> We've had a chat about this internally and there is a little bug here. You
> shouldn't have "anything" where you currently have "everything" :-) This is
> a subtle SPARQL spec oversight on our part.
>
Thank you, I'm relieved now :)
Alexandre.
> "If there is no |FROM| clause, but there is one or more |FROM NAMED|
>> clauses, then the dataset includes an empty graph for the default graph."
>>
>> Is this the expected (not "excepted", sorry) behaviour ?
>>
>
> In a nutshell, yes :-)
>
> FROM NAMED does not implicitly negate the existence of
t :
SQL> SPARQL SELECT * FROM NAMED <http://test1> WHERE { GRAPH ?g { ?s ?p ?o }
};
Now I have triples from <http://test1> only.
Is this the excepted behaviour ?
Alexandre Bertails, Atos Origin - Open Source Center.
Dump the corresponding SQL query and change every occurrence of 'WHEREDB' by
'WHERE DB' (missing only a space character). Try again with this new SQL
query and we have the expected result.
The problem arrives as soon as we use the GRAPH keyword.
Alexandre Bertails, Atos Origin - Open Source Center.
11 matches
Mail list logo
