View Issue Details

IDProjectCategoryView StatusLast Update
0007324mantisbtfilterspublic2008-04-19 05:05
ReporterGoga Assigned Tovboctor  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.3 
Fixed in Version1.1.0a1 
Summary0007324: Sorting of issues list (filters) does not work after upgrade to MySQL 4.1.21
Description

Sorting of bug list (filters) does not work after upgrade to MySQL 4.1.21.

When I click 'View Issues' I see a list having no noticible sorting. I seems unsorted at all. Clicking on header of table changes header (arrow direction), but list is still unsorted.

TagsNo tags attached.

Relationships

has duplicate 0007369 closeddregad Possible different sorting failure 

Activities

jjhowey

jjhowey

2006-08-02 18:05

reporter   ~0013183

I experience the same with MySQL 4.1.16 and Mantis 1.05. When i sort by Updated, it doesn't seem to take Ascending/Descending.... Priority should be raised to High.

alinsusan

alinsusan

2006-08-17 05:52

reporter   ~0013282

I have the same problem on 4.1.21 (slackware 10.2 + up to date stable patches)

lioxa

lioxa

2006-08-17 06:24

reporter   ~0013283

Same problem - after my host provider has upgraded MySQL to 4.1.21 - sorting stopped working completely. All bugs are sorted by number, ascending, in the bug list view. Problem first appeared on Mantis 1.0.0rc4, remained after upgrade to 1.0.5. Version of PHP - 4.4.2.

lioxa

lioxa

2006-08-17 06:51

reporter   ~0013284

Just found out that it has something to do with DISTINCT keyword in query:
"SELECT DISTINCT mantis_bug_table.* FROM mantis_bug_table WHERE mantis_bug_table.id in (...) ORDER BY last_updated DESC, date_submitted DESC"

When this keyword is removed, MySQL returns properly sorted results (if not - results are being sorted by Id).

lioxa

lioxa

2006-08-17 07:04

reporter   ~0013285

Ok, done a crude hack - removed DISTINCT from line 856 of filter_api.php. Not sure what consequences will be, but i'm desperate. :)

DONT DO THIS AT HOME! (if you're not sure what are you doing)

guestusr

guestusr

2006-08-17 09:45

reporter   ~0013288

We have the same problem (after MySQL was updated to 4.1.21-standard). After we've done what lioxa said, everything seems to be fine but - as he said as well - we don't know the consequences yet. Hopefully a solution will be found soon.

w_moroz

w_moroz

2006-08-18 09:07

reporter   ~0013296

The bug has been reported to mysql developers

http://bugs.mysql.com/bug.php?id=21456