Calling the mysqlbd rollback only rolls back the last command called. So, if one of the multiple SQL commands fails, the ones called before it won't be rolled back. This can cause inconsistency in the Webwork database.
3 Options:
- Fix the database by adding foreign keys and cascading deletes in the right places. Might break the Webwork Perl code...but shouldn't in theory.
- Create SQL functions that can be called that wrap all the SQL calls in 1 transaction.
- Try php scripts? Maybe it has something that can handle multiple commands in a transaction.
Calling the mysqlbd rollback only rolls back the last command called. So, if one of the multiple SQL commands fails, the ones called before it won't be rolled back. This can cause inconsistency in the Webwork database.
3 Options: