filter_api.php, add following after 771L

$t_join ='';

"$t_join" is used in $query and $query3, but it isn't initialized after $query is executed.

related/duplicate issues: 0007427, 0007416

seiji, can you provide more information about the location, e.g. function name, provide an extract from the code, since the lines have shifted since then. I also have a feeling that this is fixed in the latest code.

Hi,
954L in filter_api.php (1.147 CVS)
replace
for ( $i=0; $i < count( $t_sort_fields ); $i++ ) {
with
$t_join = '';
for ( $i=0; $i < count( $t_sort_fields ); $i++ ) {

sample of query2(989L)

before:
query2 = SELECT mantis_bug_table.* FROM mantis_bug_table LEFT JOIN mantis_bug_monitor_table user_monitor ON user_monitor.bug_id = mantis_bug_table.id WHERE mantis_bug_table.id in (7) ORDER BY last_updated DESC, date_submitted DESC

after:
SELECT mantis_bug_table.* FROM mantis_bug_table WHERE mantis_bug_table.id in (7) ORDER BY last_updated DESC, date_submitted DESC

it works for me.

I just added myself on the monitor list of this bug and I can confirm the problem is still there.

I can now see 8 instances of this bug in the "Monitored by me" pane.

It does not seem casual there are exactly 8 users monitoring this bug...

I'm going to produce a patch based on seiji indications

It seems this regression was introduced in revision 1.144 of filter_api.php, supposedly fixing 0007324; relevant diff:

@@ -875,7 +875,7 @@
$t_order = " ORDER BY " . implode( ', ', $t_order_array );
$t_select = implode( ', ', array_unique( $t_select_clauses ) );

• $query2 = "SELECT DISTINCT $t_select
• $query2 = "SELECT $t_select
  $t_from
  $t_join
  $t_where

So. It seems the problem in 0007324 was actaully a MySQL bug, and it was fixed in 5.0.25 and 4.1.22.

I reverted the change (added DISTINCT clause) and the "Monitored by me" list is now correct, while 0007324 is not back (Fedora 6 has MySQL 5.0.27)

If needed, I can provide the (trivial) patch