| 1 |
Jason Stubbs wrote: |
| 2 |
|
| 3 |
>On Monday 12 September 2005 00:05, Francesco R wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>http://dev.gentoo.org/~vivo/doc/mysql-update.html |
| 7 |
>> |
| 8 |
>> |
| 9 |
> |
| 10 |
>With step 2, you should probably mention the issues that can arise with |
| 11 |
>non-ASCII data in char fields. The character set really needs to specified |
| 12 |
>in the dump. After the upgrade to 4.1, the default charset of the server |
| 13 |
>should be set to something compatible and then the charset of the data |
| 14 |
>should be specified to mysql when re-importing the backup. |
| 15 |
> |
| 16 |
> |
| 17 |
--default-character-set=charset |
| 18 |
should be that of my.cnf config file, mysqldump don't permit an atomic |
| 19 |
setting of this variable. |
| 20 |
The only option for this kind of users is to atomically dump the tables |
| 21 |
and then concat the results. |
| 22 |
|
| 23 |
Importing in mysql-4.1 it's ok, provided your default character set is utf8. |
| 24 |
|
| 25 |
Russian, asian whatever person has experience on this please speak now |
| 26 |
to correct what affermed here. |
| 27 |
|
| 28 |
>Just another one of the many gotchas... |
| 29 |
> |
| 30 |
> |
| 31 |
> |
| 32 |
expand this please |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives