-
Notifications
You must be signed in to change notification settings - Fork 10
Not hide atoms #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Not hide atoms #24
Conversation
|
I n this comment: #15 (comment) I'm trying to say that you do not need to actually write the "-2" out to the database. That is because the pre-remove and the post-remove calls will come, one right after the other, in the same thread. You'll always know exactly which atom it is, and in what state it is in, so you don't need to write anything out. Did I miss something? |
|
Please note my answer |
|
The design driving this is described in issue #15 |
THIS IS A DRAFT! DO NOT MERGE!
This code is work in progress and I might still have some misconceptions.
The main thing happens in
RocksStorage::postRemoveAtominopencog/persist/rocks/RocksIO.cc: Look if we have marked an entry in Rocks (atm still '-2', but this can be changed as mentioned earlier). Then check in AS if it is absent and delete if necessary.This is not meant to compile yet and some smaller parts might still be missing...