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

refactor: Transactional trigger set #4489

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Erigara
Copy link
Contributor

@Erigara Erigara commented Apr 22, 2024

Description of the Change

As for WSV, make trigger set make trigger set transactional.

Issues

Closes #4378

Benefits

For large amount of triggers and frequent trigger execution transactional model allow not to clone trigger set all the time saving time and space.

Possible Drawbacks

Might be not so efficient when there is small amount of triggers.

@Erigara Erigara added iroha2-dev The re-implementation of a BFT hyperledger in RUST Refactor Improvement to overall code quality labels Apr 22, 2024
@Erigara Erigara self-assigned this Apr 22, 2024
dima74
dima74 previously approved these changes May 7, 2024
core/src/smartcontracts/isi/triggers/set.rs Outdated Show resolved Hide resolved
@Erigara Erigara force-pushed the transactional_trigger_set branch 2 times, most recently from 38e3c91 to d1dc4ed Compare May 8, 2024 08:55
@Erigara Erigara changed the title [refactor] #4378: Transactional trigger set refactor: Transactional trigger set May 8, 2024
Signed-off-by: Shanin Roman <shanin1000@yandex.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
iroha2-dev The re-implementation of a BFT hyperledger in RUST Refactor Improvement to overall code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[refactor]: Make trigger's set transactional as world and state
2 participants