Bug #91
Request submission needs database transactions
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | Anonymous | % Done: | 0% | |
Category: | ProCKSI | |||
Target version: | 9.0 | |||
Resolution: |
Description
When submitting a new request, we want to either have ALL data (request data, structures, tasks) committed to the database or none. If there was an error, we can make a rollback and can try to resubmit again. Without transactions, the request data may have already successfully been committed on the first time, which prevents it to be added during the subsequent commit as it would result in a duplicate entry for the request's home directory.br
Solutionbr
We need transactions and a manual commit.br
BUT: In all Database classes, 'commit' is already hard-coded so that it is done automatically.