0007071: mismatch on field names between app and database - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0007071	mantisbt	sql	public	2006-05-09 16:02	2007-08-02 02:31

Reporter	jandreaatsatlantic	Assigned To	grangeway
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	unable to reproduce
Product Version	1.0.1

Summary	0007071: mismatch on field names between app and database
Description	Error message of Database query failed. Error received from database was #1054: Unknown column 'email_on_new_min_severity' in 'field list' for the query: UPDATE mantis_user_pref_table... But looking in that table the field names are of the format emailon...minimum...
Additional Information	Affected code is in account_prefs_inc.php, account_prefs_update.php (unless the db definition has changed) and do not appear to have changed from 1.0.1 to 1.0.3.
Tags	No tags attached.

jandreaatsatlantic 2006-05-09 16:52 reporter ~0012801	Workaround: hack up a str_replace on $var inside core/user_pref_api.php/function user_pref_update.

jaymcd 2006-06-19 15:01 reporter ~0012994	If you change the field names back to "...min..." the problem seems to resolve. What is the correct DB naming?

thraxisp 2006-07-19 15:54 reporter ~0013121	It appears that you did not run the database upgrade script between 0.19.x and 1.0.x. This is the file admin/upgrade.php.

grangeway 2007-07-15 18:39 reporter ~0015004	Thank you for taking the time to report a problem with mantis. No feedback has been provided on this issue - since this problem report was originally made, a number of releases have occured. It appears that this issue has either been fixed, or may not be a relevant report for the current release. Please download the latest release from http://www.mantisbt.org/download.php [^] If you are able to reproduce this bug in the current release, or have some more information on how this feature could be improved in the current release. Please either change the mantis version on this bug report to the version you tested and change the status back to "Open", or open a new issue report wit more information. Again, thank you for your continued support and report. Paul