Re: [Virtuoso-users] How to deal with partially executed SPARQL updates?

Hi, I investigated the partially executed SPARQL updates a bit more and it turned out that I had incorrect assumptions about the updates. The updates I used were executed in a paged manner (LIMIT/OFFSET) and modified the bindings selected by their WHERE clauses, so that their paging wasn't stable

Re: [Virtuoso-users] How to deal with partially executed SPARQL updates?

On 10/30/16 10:50 AM, Jindřich Mynarz wrote: > > the behaviour you describe is what I'd like to be able to rely on. (In > fact, it's the opposite of the Anytime query.) Updates should either > be executed completely or fail transparently, so that the incomplete > execution may be handled. > > I

Re: [Virtuoso-users] How to deal with partially executed SPARQL updates?

Hi, the behaviour you describe is what I'd like to be able to rely on. (In fact, it's the opposite of the Anytime query.) Updates should either be executed completely or fail transparently, so that the incomplete execution may be handled. I will have to test this properly to ensure that partial

Re: [Virtuoso-users] How to deal with partially executed SPARQL updates?

Hi Jindřich, To my knowledge the Virtuoso Anytime query feature was only ever implemented for SPARQL select queries and not SPARQL updates, as indicated at: http://docs.openlinksw.com/virtuoso/anytimequeries/ Best Regards Hugh

[Virtuoso-users] How to deal with partially executed SPARQL updates?

Hi, how do you deal with partial SPARQL updates? I'm currently simply retrying if Virtuoso returns the HTTP header X-SQL-State with the value S1TAT (as documented in https://www.openlinksw.com/weblog/oerling/?id=1494). However, it seems that the absence of this header in SPARQL update responses