I recently updated my forum software from 3.6.5 to 4.2.2. Things are working well in the forums, but I continue to have daily emails identifying database errors. I will identify one here and the second in another post. Here is the first... and it just came in two seconds ago. I have no idea what to do with this. I will appreciate any guidance.
4.2.2 Recurring DB Errors - 1 of 2
Collapse
X
-
Tags: None
-
When vBulletin creates a new table in the upgrade process, it asks MySQL what the default collation for the database is and then uses that. Most MySQL installations default to latin1_swedish_ci. If you have changed collations for any reason on tables in the past then you should change the database to use that as the default to prevent this issue from happening in the future.
You will find more information in the MySQL manual here:
You will need to use phpMyAdmin and make sure that all tables and fields within them have the same collation. Make sure your database collations are appropriate and consistent throughout the entire database. You need to use program like phpmyadmin to view your collations:
When you click your database name in phpmyadmin it will list all tables, their collations, as well as the collation of the database itself at the bottom. And when you click the name of a table on the left it will list the collations of individual fields within that table.
1) To edit the collation of the database itself you need to click the database name on the left and then click "Operations" on the top.
2) To edit the collation of an individual table you need to click its name on the left and then click "Operations" on the top.
3) To edit the collation of an individual field within a table you need to click the table name on the left and then click the edit image (a little pencil icon) for that field.
For more information please see: https://www.vbulletin.com/forum/show...ight=collation
Note: It is very very very important to make full database backups before proceeding if you are ever manually making any changes to your database, let it be issuing queries, or editing it via phpMyAdmin or any other interface. If done incorrectly, manually modifying the database can potentially cause irreversible damage to your database, and there is no way to perform a "partial restore" to restore just the part you may break.Translations provided by Google.
Wayne Luke
The Rabid Badger - a vBulletin Cloud demonstration site.
vBulletin 5 API -
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Comment