0012626: SQL Error in sorting custom field in "View Issues" page (APPLICATION ERROR #401)

ID	Project	Category	View Status	Date Submitted	Last Update
0012626	mantisbt	filters	public	2010-12-22 04:30	2011-08-05 02:31

Reporter	rhmntk	Assigned To	atrol
Priority	urgent	Severity	major	Reproducibility	always
Status	closed	Resolution	duplicate
Platform	Windows	OS	Windows	OS Version	7
Product Version	1.2.4

Summary	0012626: SQL Error in sorting custom field in "View Issues" page (APPLICATION ERROR 0000401)
Description	I am using the latest version of Mantis (1.2.4) and I got this error message every time I try to sort a custom field in my case "expected resolved date" in "View Issues" page. Database query failed. Error received from database was #1066: Not unique table/alias: 'mantis_custom_field_string_table_5' for the query: SELECT Count( DISTINCT mantis_bug_table.id ) as idcnt FROM mantis_project_table, mantis_bug_table LEFT JOIN mantis_custom_field_string_table mantis_custom_field_string_table_5 ON mantis_custom_field_string_table_5.bug_id = mantis_bug_table.id AND mantis_custom_field_string_table_5.field_id = 5 LEFT JOIN mantis_custom_field_string_table mantis_custom_field_string_table_5 ON mantis_bug_table.id = mantis_custom_field_string_table_5.bug_id AND mantis_custom_field_string_table_5.field_id = 5 WHERE mantis_project_table.enabled = ? AND mantis_project_table.id = mantis_bug_table.project_id AND ( mantis_bug_table.project_id in (12, 32, 33) ) AND ( mantis_bug_table.status=? ) AND ( (mantis_custom_field_string_table_5.value+0) BETWEEN 1 AND 1294268398).
Tags	No tags attached.

rhmntk 2010-12-22 05:04 reporter ~0027657	Additional info to reproduce this is: Create a custom field "Expected resolved date" or anything with type date go to View Issues page set a filter of Expected resolved date and then click apply Filter button. Click the "Expected resolved date" header in order to sort the bug list based on the custom field value

atrol 2010-12-22 05:06 developer ~0027658 Last edited: 2010-12-22 05:09	Have a look at the known issue 0005859 where user nimmich added a patch for a workaround.