When updating a blank node through a GraphQL mutation, the following happens:
[image: image.png] It seems that the blank node get deleted, the updated blank node gets committed, but then also the old blank node either survives or gets rewritten into the triple store as an orphan. Is that something that might be a bug in the GraphQL engine in TopBraid or do we need to add some garbage collection cleanup to manually delete these every time a blank node value gets updated? -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/topbraid-users/ae40a76b-90f3-469b-906a-3548fd5558a5n%40googlegroups.com.
