Skip to content
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

Kvstore tx #1110

Merged
merged 19 commits into from
Sep 22, 2023
Merged

Kvstore tx #1110

merged 19 commits into from
Sep 22, 2023

Conversation

timbru
Copy link
Contributor

@timbru timbru commented Sep 8, 2023

This PR makes the krill::commons::eventsourcing::kv::KeyValueStore use transactions/locking for all functions, except for migration functions where there is no clear scope or more than one scope.

@timbru timbru marked this pull request as draft September 8, 2023 15:13
@timbru timbru linked an issue Sep 11, 2023 that may be closed by this pull request
@timbru timbru marked this pull request as ready for review September 22, 2023 08:21
Base automatically changed from caobjects-tx to prep-0.14.0-rc1 September 22, 2023 12:48
src/bin/krillup.rs Outdated Show resolved Hide resolved
@timbru timbru merged commit 00e5167 into prep-0.14.0-rc1 Sep 22, 2023
18 checks passed
@timbru timbru deleted the kvstore-tx branch September 22, 2023 14:50
timbru pushed a commit that referenced this pull request Oct 17, 2023
* Use transactions for all (non-migration) functions in Krill KeyValueStore
* Reorder functions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make all KeyValueStore functions transactional
2 participants