Replies: 1 comment 10 replies
-
Hi Anand, If your use-case is this simple, then doing the Retract and Assert will be more efficient. The SPARQL Update implementation will be using the same methods under the hood, and so by doing them directly in your code you avoid the overhead of the SPARQL parser. Hope that helps! |
Beta Was this translation helpful? Give feedback.
10 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am using dotnetRDF in a constraint device and want to frequently update Triples. I see there is ExecuteUpdate which helps execute Update SPARQL on Triples. There is also another approach where I simply keep an index of Triples and Retract and Assert that particular triple for an update.
graph.Retract(triple); var updated = new Triple(s, p, graph.CreateLiteralNode(val)); graph.Assert(updated);
Which one will be more efficient? How about Transactional behavior? Any help on benchmarking or past experiences will be helpful.
Beta Was this translation helpful? Give feedback.
All reactions