Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba


Go to End

4 Posts   1366 Views


Community Member, 14 Posts

1 September 2010 at 2:11am

When I use mysqldump and then restore the character encoding is screwed up. Any idea hows?


Community Member, 88 Posts

1 September 2010 at 5:23am

You can specify a character set encoding for dumping mysql data. by default it is utf8 (at least on my system). this might be not the encoding silverstripe created your tables with.


Community Member, 14 Posts

25 October 2010 at 11:42pm

Mysql has a double encoding problem, screws up the characters of you upgrade and use:
MySQLDatabase::set_connection_charset('utf8'); Which I hadn't tried to remove.


Forum Moderator, 1899 Posts

25 October 2010 at 11:46pm

add 'SET sql_mode = 'ANSI';' to the top of the script before running it?

also I'd suggest using...