From: Uma Bhat (bhat.umagmail.com)
Date: Sun Jun 07 2009 - 21:29:24 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Thank was great piece of info Ewen, Thanks!

However this approach works for new data. But the existing data in the
database does not show us the Japanese characters from application side.

Appreciate responses who 'actually' got to work on this conversion.

Thanks!
Uma

On 6/1/09, ewen fortune <ewen.fortunegmail.com> wrote:
>
> Uma,
>
> On Mon, Jun 1, 2009 at 8:41 AM, Uma Bhat <bhat.umagmail.com> wrote:
> > Hi All,
> >
> > I have read many blogs suggesting some examples for this.
> > But suggestions from you guys who have ACTUALLY worked on such a scenario
> > would help me out the best.
> >
> >
> > Current Database has:
> > DEFAULT CHARACTER SET - latin1
> > DEFAULT COLLATION : latin1_swedish_ci
> >
> > We need to convert this to
> > DEFAULT CHARACTER SET - utf8
> > DEFAULT COLLATION : utf8_general_ci
> >
> >
> > Note that this has to be done on a database that has *existing data* in
> it .
> >
> > Hence just by doing a:
> >
> > ALTER DATABASE <dbname> CHARSET=utf8;
> >
> > would result in unexpected behaviour of the data.
>
> Ryan Lowe blogged about this.
>
> http://www.mysqlperformanceblog.com/2009/03/17/converting-character-sets/
>
> He wrote a tool for it (linked from post)
>
> http://www.pablowe.net/convert_charset
>
> And Schlomi Noach commented that openark also has a tool.
>
> http://code.openark.org/forge/openark-kit
>
> Cheers,
>
> Ewen
>
> >
>
> > Thanks!
> > Uma
> >
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]