PHP error suppression command?

[G-man]

Is there an error suppression command I can add to the upgrade script?


Here is what my hosting company has to say about the use of the ALTER Command:

Detail: Our implementation of MySQL keeps a cached version of the database in system memory when a connection to the database is made, so that queries on the database can be executed much more quickly. When the ALTER command is executed, it modifies the actual MySQL database that you instruct it to modify, but the cached version of the database is not updated. Therefore, after the ALTER command modifies the database, MySQL compares the cached version to the actual database, realizes that they do not match, and breaks the connection to the database. This destroys the cached version in memory, and therefore removes any inconsistencies between the two.

Solution: The ALTER command does make the proper modifications to the MySQL database, and the error produced by MySQL about the connection being lost to the database can be ignored. For further database interaction, the connection to the database must be re-established.

For scripts that use the ALTER command, error suppression must be used to catch the 'lost connection error', so that the script does not exit on the error it receives.

_______________
Thanks ahead of time?

[Sharg]

Our implementation of MySQL keeps a cached version of the database in system memory

Thats interesting.

[Freddie Bingham]

If you look at the upgrade script you will see sections that do suppress errors when checking for hacks.

Search for errorno

[G-man]

Searched upgrade1.php and cannot find errorno anywhere.

[Mike Sullivan]

errno actually.

[Freddie Bingham]

This is the command to turn error reporting off:

$DB_site->reporterror=0;

You could place that before each instance of

doqueries();

YMMV

[G-man]

Okay I am an idiot. Where do I place this to get it past the problem my server has with ALTER listed above?

"For scripts that use the ALTER command, error suppression must be used to catch the 'lost connection error', so that the script does not exit on the error it receives. "

[G-man]

Freddie, Ed,
Don't forget me. I have 25000+ people waiting on the new version.

[Freddie Bingham]

I told you what you could try in my last post..If your mysql implementation is how your host says it is than I think you would be the first vB user to ever have this problem as previous upgrades have used the ALTER command.

Find every instance of doqueries(); in upgrade1.php

Place $DB_site->reporterror=0; on the line before it. Alot of the queries don't ALTER but some code turns the error reporting off than back on so you need to do as I said to make sure the error reporting stays off for you throughout the script.

[G-man]

Blame it on Vservers....

[Freddie Bingham]

I know there are other vB owners on Vservers who do not have this problem.

[G-man]

Frankly I would like to hear from some of them because the text I posted was directly from their FAQ and was pointed out by a senior tech after 9 hours of trying to get your upgrade script to work.

[G-man]

Thank you for getting me past those darn errors but now it looks like I have other problems:

Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

[Freddie Bingham]

What step gave you that error.

[G-man]

Step 4

Right here:

Updating data in forum table


Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

Dropping category table

Altering forum table


Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

Next step -->