-
Notifications
You must be signed in to change notification settings - Fork 7
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
adding and removing keys should be logged in order to the journal #384
Comments
I thought this would be fixed by using an OrderedDictionary in the skip list dictionary but that is already the case. |
"in order" means which order? The OrderedDictionary is sorted by when the key was added, not in the order that they are later in the index (see #415 ) |
with remove and add being in two different dictionaries, there is no order between them: we log first all adds, then all removes. This can lead to the order between add and remove passible being wrong ("add, remove, add remove" is logged as "add add remove remove") |
Now SoilIndexedDictionary uses newValues removedValues just for creating the journal. To have the Journal in correct oder, we need to instead have one OrdredCollection that stores both add and removes. But this list need to be condensed to not log multiple adds/remove for the same key |
Note from discussion:
|
No description provided.
The text was updated successfully, but these errors were encountered: