Hi Catrina
I am working on related area as we speak.
I believe the correct behavior would be:
For either an add or delete operation,
if either there is no such variable
or the variable is bound but points to a graph that cannot be
found in the workspace
(either because it is does not exist at all, or exists
on the web)
then an error should be reported, and no change should be made.
That seems like six tests to cover this area.
I take it you are working with a TBE or SDK client, rather than a Web
service.
Jeremy
On 9/17/2010 11:36 AM, Catrina wrote:
I have a SPARQLMotion script that contains PerformUpdate modules for
INSERTs and DELETEs where the graph being updated is set dynamically
using urn:var. If I incorrectly set this graph, an error is only
occuring where the PerformUpdate module is attempting a DELETE. There
is no error shown when the graph variable is set incorrectly for
PerformUpdate modules attempting an INSERT.
For example, a PerformUpdate DELETE error shows the following from
Composer:
Could not execute SPARQLMotion script
No such graph: urn:var:upOntBaseURI
While a PerformUpdate INSERT shows no error at all. The script
appears to have run successfully even though the inserts didn't make
it to any graphs in the project's workspace.
Thanks,
Catrina
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
