Ran into an issue where a quad that is reinserted (added, deleted, added again), can not be deleted a second time, this occurs in boltdb, and level db, works without issue with memstore. Originally reproduced using cayley as an application (http intrface), but now have a simple test case that I have added here:
Just wanted to check if the preference is to log issues directly into github, or if the preference is to vet through discourse first. Not sure if I needed to add any tags to that issue?
Update: Updated the github issue with what I believe the issue is and the change that would be needed, first time with go, and looking at cayley source, wouldn’t mind if someone in the know could take a look and see if the change seems reasonable.