MySQL Bugs: #14357: Issue #xx could not be found

Bug #14357	Issue #xx could not be found
Submitted:	26 Oct 2005 20:25	Modified:	3 Nov 2005 6:04
Reporter:	Mehdi Sidi Boumedine	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Eventum	Severity:	S1 (Critical)
Version:	1.6.0/1.6.1	OS:	Linux (Linux (Fedora))
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I've just installed eventum 1.6.1. I enjoy the administration interface. After creating a group and users, I created an issue. I have been naturally directed to a page where I could choose "Open the new issue details". When I choose this option, it directs me to a screen "Issue #1 could not be found".
I created other issues with the same result. I went to the issue list: nothing. I searched, filtered, displayd all, nothing.
I checked in the DB, issues are there. 
The only place where issues are shown are pie charts, and general reports confirm that issues exist.
Note I have'nt created a project, but only used the default one.

How to repeat:
Install PHP 4 on linux
Install MySql 4 on linux
Install eventum, set it up
Create users, create a group
Create an issue, try to display it somewhere :)

Hi,
are there any errors in the error log? The error log is located in /path-to-eventum/logs/errors.log

Error log for no issue displayed

Attachment: errors.log (application/octet-stream, text), 7.75 KiB.

The log in the attached file above is for 1.6.1 version. Thanks

Hi Bryan,
May be this is the fix for this problem.

The native mysql error message is : 1054 ** Unknown column 'iss_pri_id' in 'on clause'

I run the query in mysql client it gives the same message though iss_pri_id field is prensent in issue table. 

The portion of sql is the one above :

                FROM
                    eventum.eventum_issue,
                    eventum.eventum_project
                 LEFT JOIN
                    eventum.eventum_project_priority
                 ON
                    iss_pri_id=pri_id

If you permute the order of eventum_issue and eventum_project like below, the sql works fine :

                 FROM
                    eventum.eventum_project,
                    eventum.eventum_issue
                 LEFT JOIN
                    eventum.eventum_project_priority
                 ON
                    iss_pri_id=pri_id

Could this be the only problem ?

This is a duplicate of bug #13161. The problem is caused by a change with MySQL 5 to be more standards compliant.

Mehdiiiii