Forum Moderators: coopster
My question is:
How can I be sure that the backup will be properly achieved before the del happens and could a race exists where the winner will be the del action due to time to backup requirement obviously longer than a simple del query
Or am I looking at the wrong solution
Or perhaps you could invoke a 'Confirm Delete' page? That would force the user to review their option before actually executing it.
Just some ideas...
However I will do first the “Double Check” for that one operation
(I am already too far in the project to transform my queries to
MyISAM in queries aiming at an Inno DB form that I never (yet) used)
And presently looking at your suggestions
To simulate transactions, you might use table-locking and your own error-handling, so you create a script that will use dynamic variables to accomplish the task at hand, keep the script/function separate so that you can use it from all over the place in different scripts as required.