[ic] UTF-8 in MySQL

[Elver Loho]

Okay, this is what shows up in the mysql log:

060307 16:50:00   56124 Connect     user at host on system
                  56124 Query       set autocommit=1
                  56124 Query       select * from locale limit 1
                  56124 Query       select * from locale
                  56124 Quit

That is interchange connecting to the database and grabbing the
translation tables.

What it should do is issue 'set names utf8' or 'set character set
utf8' before anything else.

in dbconf/locale.mysql it is defined as:

Database  locale  locale.txt SQL
Database  locale  DSN dbi:mysql:system:host_ip
Database  locale  USER user
Database  locale  PASS pass

Database  locale  KEY           code
Database  locale  COLUMN_DEF    "code=varchar(255) character set
latin1 collate latin1_bin not null default ''"
Database  locale  COLUMN_DEF    "en_US=text character set latin1"
Database  locale  COLUMN_DEF    "eng=text character set latin1"
Database  locale  COLUMN_DEF    "lat=text character set utf8"
Database  locale  COLUMN_DEF    "lit=text character set utf8"
Database  locale  COLUMN_DEF    "rus=text character set utf8"
Database  locale  COLUMN_DEF    "est=text character set latin1"
Database  locale  COLUMN_DEF    "comments=text character set utf8"
Database  locale  COLUMN_DEF    "id=int primary key auto_increment"

There any way to tell it to issue 'set names utf8' after connecting?


Elver

On 3/7/06, Elver Loho <elver.loho at gmail.com> wrote:
> On 3/7/06, Stefan Hornburg <racke at linuxia.de> wrote:
> > Elver Loho wrote:
> > > Hiya!
> > >
> > > We have a problem here implementing i18n support for our webshop. That
> > > is, right now, things 'work' in that we have a MySQL database with all
> > > our products in it, including some product names in Russian.
> > > (Cyrillic, UTF-8 fields.)
> > >
> > > However, on the MySQL side, those database fields are currently set as 'latin1'.
> >
> > I recommend to store UTF-8 as UTF-8 and go from there. Interchange might cause
> > trouble them, but we can fix that side. And IMHO it is most important that your
> > data base is clean.
>
> Um, dude. That's the problem right now with our new table. We're
> storing UTF-8 text as UTF-8 in the database. Interchange doesn't issue
> 'set names utf8' or 'set character set utf8' in order to read those
> fields. How can we tell it to?
>
>
> Elver
>