I did [:"red"] NOT [/] naturally hit the reload button.
I watched the mysql demon, via top. When it stopped, I just went on with the upgrade, manually changing the url to the next step. What else could I have done?
Also there was no clear warning that timeouts were likely and would screw up the database. I think these altertables should be made with timeout in mind, sort of timeout proof. See below.
Then when the board showed all kinds of error messages, I checked what parts had not been done, and redid this step.
After a few iterations, I had redone most steps of the altertable 6.1 6.2 as half of these steps had timed out.
I think there is an inherent problem: I think after a web server timeout, the processes started by it get killed. Does not make sense to allow a bunch of runaway processes continue forever while their output will never reach the web page
So this is what causes the problem.
[:"red"] So I suggest to reconsider my suggestions:
[/]
a) provide altertables also in mysql command format and/or php command line format. Even people with shared web servers can ask admin to run one routine for them once a year!!
b) Keep "DROP" commands for a later time, when we have tested all the upgrade. This way no information gets lost. so it is easy to re-run just one part of the altertable again. In other words, use an altertable/addtable routine, and only much later a droptable routine.
Please make altertable routines "timeout proof"!!
Long altertables that time-out should be made in a way that they can be redone with no problem.
Something like: for all rows where UID is not equal to default keep processing.
This way that process can be redone various times. And it will skip the part that already has been done, so eventually it will end.
Also, before starting a step, the altertable should give clear instructions what to do in case of a timeout or other problems. Actually, it should be in a way that reload will solve.
What do you expect a regular user, without telnet, to do after he gets the "server not found" or whatever timeout error message??? sit for how many hours doing nothing? or get to the next step of the altertable how?
There are only 2 naturally possible reactions. "Reload" or "Back". Both seem quite fatal!! I guessed the url for the next step and typed it in manually. I still do not know what should have been done!?
I finished this, so it is of no maior concern to me. I write this more so infopop can improve their documentation and procedures, to make them userfriendly.
So people can follow them without having to spend 5 hours of detailed study of the altertable programming details, and another 5 hours pouring over the board to find if there are any issues.
