0004186: Some upgrade scripts do not read table names from config - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0004186	mantisbt	upgrade	public	2004-07-24 16:26	2004-08-29 02:00

Reporter	Jordi	Assigned To	jlatour
Priority	normal	Severity	block	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	0.19.0a2
Fixed in Version	0.19.0rc1

Summary	0004186: Some upgrade scripts do not read table names from config
Description	It seems that the update proces does not read tablenames from the config_default nor config_inc files. If you personalized the tables prefix, or any table name, during the update process you get an error, and update finish after half/updating Upgrading from 0.18.3 you get this error: Add sponsorship_total to bug table sponsorship-2 ERROR: Table 'mantis.mantis_bug_table' doesn't exist
Additional Information	The table name was personalized in 0.18.3 and now the table is named devel_bugs Vars in config_inc AND config_default are configured: $g_db_table_prefix = 'devel'; $g_mantis_bug_table = $g_db_table_prefix.'_bugs';
Tags	No tags attached.

Jordi 2004-07-24 16:35 reporter ~0006338	If you go renaming the table to the old name, just to be able to run the update, you're getting a message for each table being updated: Add real name to user information. user_realname ERROR: Table 'mantis.mantis_user_table' doesn't exist Allow custom fields to be set/required for resolve/close/report/update custom_fields-1 ERROR: Table mantis.mantis_custom_field_table' doesn't exist Remove project_id+version primary key version_remove_pk ERROR: Table 'mantis.mantis_project_version_table' doesn't exist Finally ... yo get an error: Fatal error: 401 in core/database_api.php on line 101

jlatour 2004-08-07 09:58 reporter ~0006766	Most upgrade scripts do use the config, but not all of them. Needs to be reviewed.