129: database tables should be created with UTF-8 columns instead of the default collation

Notes
(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.

(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.

(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.

(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.

(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 ]