Both of these errors have been fixed in CVS since the alpha was released.
It appears that most of the developers were testing on the new version, and
these slipped through. They are covered in issues #5450 and #5457 in the
A new alpha will be coming out soon.
On 4/21/05 8:56 AM, "Grant McHerron" wrote:
> Hi Folks,
> I just went to install Mantis 1.0.0a1 on a machine running PHP 4.1.2 and
> mySQL 3.23.54. Given the installation documents said that it'd work with
> MySQL 3.23.2 and higher
> (http://manual.mantisbt.org/manual.installation.php) we figured we
> should try it.
> Unfortunately, the mySQL version requirements appear to be inaccurate,
> as per the two issues below:
> First, the db_generate.sql script refused to work until we pulled out
> all the "ENGINE=MyISAM DEFAULT CHARSET=latin1" bits.
> Second, once in things seemed to work until I went to edit a project I'd
> just created
> (http://oursite/mantis/manage_proj_edit_page.php?project_id=3). The
> system responded with the following error:
> APPLICATION ERROR #401
> Database query failed. Error received from database was #1064: You have
> an error in your SQL syntax near '( mantis_project_table p LEFT JOIN
> mantis_project_user_list_table l ON p.id=l.pr' at line 3 for the query:
> SELECT DISTINCT u.id, u.username, u.realname, u.access_level as
> access_level, l.access_level as override
> FROM mantis_user_table u LEFT JOIN
> ( mantis_project_table p LEFT JOIN mantis_project_user_list_table l ON
> p.id=l.project_id AND p.id = 3 )
> ON l.user_id=u.id
> WHERE ( ( u.access_level >= 0 )
> OR ( l.access_level >= 0 AND l.user_id=u.id )
> OR u.access_level>=90 )
> AND u.enabled = 1
> AND p.id = 3
> Am I doing something wrong with all this or is Mantis now expecting SQL
> 4 to operate?