Wondering if this will always be free? See why free is better.
Started by JayBachatero, January 08, 2007, 09:39:10 PM
sed -r 's/latin1/utf8/g' dump.sql > dump_utf.sql
SET NAMES utf8
SET NAMES 'utf8'
Quote<H> I had zero posts when I started posting
Quote from: Sarge on August 19, 2007, 07:52:57 AMBe sure to export and import the database with the correct charsets:http://textsnippets.com/posts/show/84 [nofollow]The sed syntax posted in the link above has never been correct for me in CentOS and Ubuntu (invalid arguments, I think), but the alternate syntax (posted in the last comment) always worked fine:Code Select Expandsed -r 's/latin1/utf8/g' dump.sql > dump_utf.sqlIf you can't import because you don't have shell access, you can addCode Select ExpandSET NAMES utf8orCode Select ExpandSET NAMES 'utf8'at the start of the database dump file. If you do this, save the dump file in the correct charset! Alternatively, use/modify a restore script that can "SET NAMES utf8" when importing.
Quote from: al0000 on August 27, 2007, 06:20:14 PMAny idea why i get a "Hacking attempt..." message when i try to convert to UTF8?
Quote from: CSpili on September 01, 2007, 08:02:09 AMyou've got PM Sarge
path-to-sed s/latin1/utf8/g path-to-db-backup.sql > path-to-db-backup-sed.sql
"C:\Program Files\GnuWin32\bin\sed" s/latin1/utf8/g C:\backup.sql > C:\backup-sed.sql