Notice: this is a static mirror for historical purposes.

View Issue Details Jump to Notes ] Related Changesets ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
129Source Integration[All Projects] Generalpublic2010-04-08 02:582010-04-08 15:00
Assigned ToJohn Reese 
Product Version 
Target Version0.16Fixed in Version0.16 
Summary129: database tables should be created with UTF-8 columns instead of the default collation

When installing the source integration plugins, the default collation for the database is used, instead of using UTF-8
This leads to inconsistencies inside the mantis database because Mantis itself uses UTF-8 (utf8_general_ci under MySQL), both in the database and the sources.
This also means that the data inserted for changeset messages will be wrong if accented characters are present.
TagsNo tags attached.
Attached Files

- Relationships
related to 130assignedJohn Reese SVN plugin should decode svn output 

-  Notes
User avatar (156)
obones (reporter)
2010-04-08 06:21

A side effect of this is that values have to be encoded in UTF-8 (with utf8_encode) before they are sent to the database. But this ensures that all special characters are stored correctly.
User avatar (160)
John Reese (administrator)
2010-04-08 12:28

If you need UTF8 collation, you should be setting your database's default collation to UTF8. If you need something other than UTF8, you should set your default collation to that instead. The Source Integration system should not be trying to be smarter than your database configuration.
User avatar (161)
obones (reporter)
2010-04-08 12:32

I understand that, and I was kind of expecting this answer.
But to me, the plugins should be consistent with what Mantis itself is doing. And right now, it creates the tables with UTF-8 regardless of what the default is for the database.
But I also understand you not willing to spend time on this as it is indeed a matter of setting up the database correctly.
User avatar (164)
John Reese (administrator)
2010-04-08 12:49

You are correct. Apparently MantisBT was updated when I wasn't paying attention to set default table collations to UTF8. I will agree that consistency with the core behavior is preferable.
User avatar (169)
John Reese (administrator)
2010-04-08 15:00

Fix committed to master branch at 2010-04-08 21:44:45.

- Related Changesets
Source Integration: master f929e745
Timestamp: 2010-04-08 21:44:45
Author: John Reese
Committer: John Reese
Details ] Diff ]
Fix 129: Set default table collation to utf8
mod - Source/Source.php Diff ] File ]

- Issue History
Date Modified Username Field Change
2010-04-08 02:58 obones New Issue
2010-04-08 06:21 obones Note Added: 156
2010-04-08 12:28 John Reese Note Added: 160
2010-04-08 12:28 John Reese Status new => resolved
2010-04-08 12:28 John Reese Resolution open => won't fix
2010-04-08 12:28 John Reese Assigned To => John Reese
2010-04-08 12:32 obones Note Added: 161
2010-04-08 12:32 obones Status resolved => feedback
2010-04-08 12:32 obones Resolution won't fix => reopened
2010-04-08 12:48 John Reese Status feedback => assigned
2010-04-08 12:49 John Reese Note Added: 164
2010-04-08 12:49 John Reese Target Version => 0.16
2010-04-08 12:49 John Reese Relationship added related to 130
2010-04-08 15:00 John Reese Note Added: 169
2010-04-08 15:00 John Reese Status assigned => resolved
2010-04-08 15:00 John Reese Fixed in Version => 0.16
2010-04-08 15:00 John Reese Resolution reopened => fixed
2010-04-08 15:00 John Reese Changeset attached master f929e745 =>

Copyright © 2000 - 2012 MantisBT Group
Time: 0.1308 seconds.
memory usage: 8,398 KB
Powered by Mantis Bugtracker

hosted with