I´m trying to upgrade the old database to my new server database.
And i have problems with the 1b point.
1b) Configure the new MySQL to use Latin1 as the default character
set everywhere, not UTF-8. This is necessary so the import in
the next step assumes the data is Latin1.
Now i have this
character set clientutf8(Valor global)latin1 character set
connectionlatin1character set database
latin1 character set filesystembinary character set resultsutf8(Valor
global)latin1 character set serverlatin1 character set systemutf8
And all the database tables or fields is in utf8_general_ci.
I´m trying to upgrade the old database to my new server database.
And i have problems with the 1b point.
1b) Configure the new MySQL to use Latin1 as the default character
set everywhere, not UTF-8. This is necessary so the import in
the next step assumes the data is Latin1.
Now i have this
character set clientutf8 (Valor global)latin1 character set connection
latin1 character set database latin1 character set filesystembinarycharacter set results
utf8 (Valor global)latin1 character set serverlatin1 character set systemutf8
And all the database tables or fields is in utf8_general_ci.
RT uses UTF8. In version prior to RT 3.8 you could have DB configured for
latin1, but still data is UTF8. This is wrong and upgrade to RT 3.8 or
newer corrects schema if properly performed.
I don’t understand what exactly is your problem.On Fri, Mar 16, 2012 at 17:41, Juanjo juanjillo@gmail.com wrote:
I´m trying to upgrade the old database to my new server database.
And i have problems with the 1b point.
1b) Configure the new MySQL to use Latin1 as the default character
set everywhere, not UTF-8. This is necessary so the import in
the next step assumes the data is Latin1.
Now i have this
character set clientutf8 (Valor global)latin1 character set connection
latin1 character set database latin1 character set filesystembinarycharacter set results
utf8 (Valor global)latin1 character set serverlatin1 character set systemutf8
And all the database tables or fields is in utf8_general_ci.
1b) Configure the new MySQL to use Latin1 as the default character
set everywhere, not UTF-8. This is necessary so the import in
the next step assumes the data is Latin1.
My Mysql is not full Latin1 to do the upgrade.If you see other emails i
have a lot of problems with the datbase migration.
I only follow the instructions to make the upgrade
Thanks.
Best Regards,El 22 de marzo de 2012 18:52, Ruslan Zakirov ruz@bestpractical.comescribió:
Hi,
RT uses UTF8. In version prior to RT 3.8 you could have DB configured for
latin1, but still data is UTF8. This is wrong and upgrade to RT 3.8 or
newer corrects schema if properly performed.
I´m trying to upgrade the old database to my new server database.
And i have problems with the 1b point.
1b) Configure the new MySQL to use Latin1 as the default character
set everywhere, not UTF-8. This is necessary so the import in
the next step assumes the data is Latin1.
Now i have this
character set clientutf8 (Valor global)latin1 character set connection
latin1 character set database latin1 character set filesystembinarycharacter set results
utf8 (Valor global)latin1 character set serverlatin1 character set
system utf8
And all the database tables or fields is in utf8_general_ci.
1b) Configure the new MySQL to use Latin1 as the default character
set everywhere, not UTF-8. This is necessary so the import in
the next step assumes the data is Latin1.
My Mysql is not full Latin1 to do the upgrade.
As far as I recall original wording was slightly different, but may be too
complicated so it was simplified. It was saying that this step is
recommended, but things can work without it. If you use binary charset when
you dump old DB and import it then it’s probably enough to avoid
corruption during dump/import even if mysql is configured for utf8. As far
as I recall 1b step is overprotective.
If you see other emails i have a lot of problems with the datbase migration.
I only follow the instructions to make the upgrade
Thanks.
Best Regards,
Hi,
RT uses UTF8. In version prior to RT 3.8 you could have DB configured for
latin1, but still data is UTF8. This is wrong and upgrade to RT 3.8 or
newer corrects schema if properly performed.
I don’t understand what exactly is your problem.
Any help?
Hello Again.
I´m trying to upgrade the old database to my new server database.
And i have problems with the 1b point.
1b) Configure the new MySQL to use Latin1 as the default character
set everywhere, not UTF-8. This is necessary so the import in
the next step assumes the data is Latin1.
Now i have this
character set clientutf8 (Valor global)latin1 character set connection
latin1 character set database latin1 character set filesystembinarycharacter set results
utf8 (Valor global)latin1 character set serverlatin1 character set
system utf8
And all the database tables or fields is in utf8_general_ci.