Non-transactional approach?

[haietza]

This plugin would be very helpful to us, but we need to enforce GTID consistency for our DB replication, so using the transactional approach for creating the temp tables throws an error when we try to run the restore script. Is there an alternative way to accomplish this? Thank you!

[pauloafpjunior]

Dear @haietza.

Thank you for your interest. Actually, our plugin is just a wrapper for the backup and restore Moodle API. Therefore, the engine that controls the database consistence is out of our scope.

However, this is an interest question, that may be the question of other ones. Hence, I think you must post it in a forum of Moodle Dev community.

Best regards.
Paulo.

[haietza]

Actually, it looks like the Moodle backup and restore is not transactional. The creation of the course is, but the backup and restore is not (we successfully use backup and restore with our database, which would not be the case if it were transactional). I think the course creation could be transactional, but the backup and restore temp tables that are created is where that becomes an issue. I wonder if there is a way to use a transaction to create the course, then do the backup and restore outside of that?