I am upgrading from 6.1 to 6.3
Problems
a) I think it is very inconvenient to do this with web based altertable routines. The web page usually timed out after 10 minutes or so. Then I just had an error message, did not know if the update step really had been done.
I watched the server activity with the top command, that kind of helped me to see when the mysql activity had died down, so I assumed that step had been finished.
So after a timeout at an url like xxxxxxx.com/ubbthreads/altertable-6.1-6.2.php?step=step3 I got an error page like "server could not be found"
So I tried a logical thing: hit the reload button. This seems to have the effect that the same step will be executed again, as suddenly the database was using up all the cpu time again, for a long time.
So instead of hitting reload on that url
xxxxx.com/ubbthreads/altertable-6.1-6.2.php?step=step4
I tried to guess the next url, like
xxxxx.com/ubbthreads/altertable-6.1-6.2.php?step=step4
then of course, I also did not get a page, but the altertable just went through its next step.
** summary:
this web based altertable with timeout is definitely not user friendly or easy to use. It does not allow to really verify if the database changes have been done correctly. Do you have another suggestion how to verify if I ended up corrupting the database? When the webserver times out, are you sure the altertable continues?
Also I had to watch the altertable constantly, without feedback. If there was some feedback (maybe execute 10 000 changed, then output a progress message), things were much easier, maybe even the timeout could be avoided.
I suggest that there should be at least a log file on the server that shows the success or failure of the altertable steps.
=====
now my problem.
while xxxxx.com/ubbthreads/altertable-6.1-6.2.php
was running, I got bored and wanted to look at then next step. So I clicked on
http://www3.xxxxxx.com/ubbthreads/altertable-6.2-6.3.php expecting I would be warned before it would execute.
Instead, in the middle of altertable 6.1 to 6.2, the altertable 6.2 to 6.3 ran. with error message as follows
=======
Altering the Posts table to store the parent user id to restore the in reply to userrname.
SQL ERROR: Wed, Jun 18 2003 12:49:56 -0400 Unable to do_query: ALTER TABLE w3t_Posts ADD B_ParentUser INT(9) UNSIGNED, ADD B_LastPosterId INT(9) UNSIGNED, ADD B_LastPostNum INT(11) UNSIGNED
Duplicate column name 'B_ParentUser'Altering the Users table to add a field for banned users.
SQL ERROR: Wed, Jun 18 2003 12:50:02 -0400 Unable to do_query: SELECT B_Uid FROM w3t_Banned
Unknown column 'B_Uid' in 'field list'
Warning: Supplied argument is not a valid MySQL result resource in /home/httpd/www3.angeles2.com/ubbthreads/mysql.inc.php on line 131
Adding a table to store languages users can choose from...
Done
The Re: Username was re-introduced with this version and will appear on new posts. If you would like to update old posts you can now run this script to update these posts. This may take a while and might time out. If it does time out you can just reload the script and it will pick up where it left off. You may need to do this several times before it actually finishes.
------------
at the end, after the (hopefully) completion of the altertable 6.1 6.2, I ran this routine again.
this time I got these error messages.
Question: what should I do now??
==========
Altering the Posts table to store the parent user id to restore the in reply to userrname.
Altering the Users table to add a field for banned users.
SQL ERROR: Wed, Jun 18 2003 14:00:06 -0400 Unable to do_query: ALTER TABLE w3t_Users ADD U_Banned INT(1) UNSIGNED DEFAULT '0', ADD U_CoppaUser INT(1) UNSIGNED DEFAULT '0'
Duplicate column name 'U_Banned'SQL ERROR: Wed, Jun 18 2003 14:00:06 -0400 Unable to do_query: SELECT B_Uid FROM w3t_Banned
Unknown column 'B_Uid' in 'field list'
Warning: Supplied argument is not a valid MySQL result resource in /home/httpd/www3.angeles2.com/ubbthreads/mysql.inc.php on line 131
Adding a table to store languages users can choose from...
SQL ERROR: Wed, Jun 18 2003 14:00:06 -0400 Unable to do_query: CREATE TABLE w3t_Languages ( L_Entry INT(9) NOT NULL AUTO_INCREMENT PRIMARY KEY, L_Language VARCHAR(255), L_Description VARCHAR(255), L_Active INT(1) )
Table 'w3t_Languages' already existsSQL ERROR: Wed, Jun 18 2003 14:00:06 -0400 Unable to do_query: CREATE TABLE w3t_Mailer ( M_Time INT(11), M_Subject VARCHAR(255), M_Message TEXT, M_Groups VARCHAR(255), M_Bogus VARCHAR(255), M_Onebyone INT(1), M_Loop INT(9), M_Type VARCHAR(10) )
Table 'w3t_Mailer' already existsDone
The Re: Username was re-introduced with this version and will appear on new posts. If you would like to update old posts you can now run this script to update these posts. This may take a while and might time out. If it does time out you can just reload the script and it will pick up where it left off. You may need to do this several times before it actually finishes.
===============
