Those instructions have been acurate and are still acurate for any backup/restore situation within the same MySQL version AFAIK. There is a bug in MySQL causing problems moving from MySQL 4.0 (and maybe before) to 4.1, and Jelsoft (not MySQL!!!) have spend a lot of time in finding what have been causing this problem and find a work around for it. The majority of the customers will never encounter this problem, only when they try to move to 4.1.
Once again the bug is in MySQL and not in vBulletin, and the reason and work around for it have only recently been found. The way your warning is put in your thread above make it looks like all vB customers will run into this issue, and that it is Jelsoft's fault that it is happening. I didn't deny the problem, i only tried to put your post in the correct perspective.
If you feel that Jelsoft makes a mistake on this issue, please contact Jelsoft about this, or post at the official support forum vBulletin.com.
vB.org has nothing to do with official support, and is not the place to make complaint about that.
07-22-2005, 12:42 PM
Threaded Mode