Skip to content
This repository has been archived by the owner on Aug 27, 2024. It is now read-only.

Check execution should happen in one DB transaction #430

Open
prayerslayer opened this issue Sep 4, 2016 · 0 comments
Open

Check execution should happen in one DB transaction #430

prayerslayer opened this issue Sep 4, 2016 · 0 comments
Labels
Milestone

Comments

@prayerslayer
Copy link
Contributor

Currently e.g. the the approval check uses different transactions when accessing the database. If there is an error somewhere, e.g. in the auditService call because we cannot write to the file, we may end up with an inconsistent database state, as already executed queries won't be rolled back.

@prayerslayer prayerslayer added this to the Zappr 1.1 milestone Sep 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant