Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [babel-dev] Babel Server Nightly mysqldump --- importing failed.
Hi,

I must admit that I've never been able to use the nightly database dump either since I made the changes as per the discussion thread you have included below.  Our current dump commands are:

mysqldump --default-character-set=utf8 -r babel-database.sql -u root babel projects languages map_files project_versions files strings translations
iconv -f ISO-8859-1 -t UTF-8 babel-database.sql -o iso_dump.sql

Using a simple mysqldump (no --default-character-set, and no iconv process of the dump file) I am able to re-import the dump into any other Linux-based MySQL server.  In fact, for our tape backup process, that is how I dump the database.

I have changed the nightly dump to do a plain mysqldump.  The next nightly build runs at 6:00am Eastern time, so in about 24 hours the dump should be complete.

Denis



Xiaohong Yin wrote:

Hello babel-dev:

 

My name is Xiaohong Yin. I am working for TIBCO Software Globalization department.

 

I am trying to import mysqldump. My babel database is utf8. However, after importing, characters are corrupted when access through the web. I check

$file –i babel-database.sql

 

It comes back charset=us-ascii

 

I had assumed that the dump will be utf8. My environment is Fedora core 9, MySQL 5.0.51a. Could someone please verify that the dump is valid?

 

 

Thanks,

Xiaohong

From: babel-dev-bounces@xxxxxxxxxxx [mailto:babel-dev-bounces@xxxxxxxxxxx] On Behalf Of Denis Roy
Sent: Friday, March 07, 2008 10:15 AM
To: Babel committers mailing list
Subject: Re: [babel-dev] Babel Server Nightly mysqldump

 

Kit,

I downloaded the file from our website and imported it into my Linux workstation's MySQL server.  Although opening the mysqldump file with a text editor, even set to utf8,  revealed incorrect characters, it imported perfectly into the MySQL server.  Using SELECT, the 20 or so translations that I looked at on my Linux box were identical to those on the server.

Perhaps if you're using Windows there's something different, but from where I sit, the dump is fine.

Denis

Kit Lo wrote:


Denis,

The mysqldump on yesterday morning still had invalid UTF-8 characters. I thought we didn't get the fix in time for yesterday's build. I waited one more day. This morning's mysqldump still looks the same.

Could you try to restore the mysqldump into a test schema and see if the translations display okay?

Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead 

 






 
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
  



-- 
Denis Roy
Manager, IT Infrastructure
Eclipse Foundation, Inc.  --  http://www.eclipse.org/
Office: 613.224.9461 x224 (Eastern time)
Cell: 819.210.6481
denis.roy@xxxxxxxxxxx

_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev

Back to the top