View Issue Details

IDProjectCategoryView StatusLast Update
0008227mantisbtdb mysqlpublic2009-01-15 11:26
ReporterMartin Fuchs Assigned Tosiebrand  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.1.0a4 
Fixed in Version1.2.0a3 
Summary0008227: MySQL compatibility
Description

The current Mantis version is only compatible to MySQL version 4.1 upwards, since it uses the SQL statement "SET NAMES" (see also report 0006782). Either the documentation should be updated accordingly, or there should be a way to configure Mantis not to use the new statement.

TagsNo tags attached.

Relationships

related to 0006782 closedvboctor MantisBT should do "SET NAMES $charset" on connect to database 

Activities

ryandesign

ryandesign

2007-08-02 18:32

reporter   ~0015331

I would be in favor of requiring at least MySQL 4.1.1 for Mantis 1.1.0. Anybody who still uses earlier versions of MySQL is waaaaaaaaaaaaaay out of date and doesn't deserve support.

However, the manual says we support back to 3.23.2:

http://mantisbt.org/manual/manual.about.mantis.minimum.requirements.php

If this is still desired, the SQL statement could be changed to:

/!40101 SET NAMES utf8 /

This will cause the statement to only execute on MySQL 4.1.1 and higher.

Ellerbrok

Ellerbrok

2007-08-09 03:32

reporter   ~0015383

Hi there,

I would favor the update of the manual. As you said erarlier versions of the MySQL are really out of date and should not be used anymore by anybody.

By using the conditioned "SET NAMES" you'll get different behavior of the system dependend on the used database. The effort for bugtrapping and debugging errors would increase a lot.

I know what I am talking about for I am a developer of large C++ projects. I am really happy every time I get rid of such a "user system dependend behavior".

Regards,
Marcel

siebrand

siebrand

2008-09-10 18:04

reporter   ~0019372

Mantis 1.2.x requires MySQL 4.1.1 since 2007-12.