update problem with defaul charset

Forum Moderators: open

Message Too Old, No Replies

update problem with defaul charset

Oliver Henniges

2:12 pm on Mar 7, 2009 (gmt 0)

I am planning to update from mysql 4 to mysql 5 on

a) my intranet server
b) my webserver

After installing mysql 5.1 on my notebook testwise, I was faced with the problem of not being able to import dump-files (from my notebook) on any of both mysql 4 environments.

It seems I made a mistake with the default sort-charset (latin-swedish OMG;), but I cannot remember to have defined this anywhere in the installation process.

Imports from 4 to 5 work perfectly fine, but not vice versa.
What exactly is the background with this feature?

What do I have to take care for if I want to update on my webserver? Will I have to copy the database to a new 5.1 Version and then redefine access-parameters (password) in all scripts to that new updated database or is there any chance to tell my hoster "please now update my mysql-version and keep the databases"?

rocknbil

3:58 pm on Mar 7, 2009 (gmt 0)

I'm not sure if I precisely understand the problem, but have experienced similar issues (I think!) when using mysql encode() and decode(). You can easily change collation:

alter database [dbname] character set latin1, collate latin1;

This can also be done table by table.

Specifying Character Sets and Collations [dev.mysql.com]

Database Collation [dev.mysql.com]

Table Collation [dev.mysql.com]

Another problem I often encounter when changing versions, "Client does not support authentication protocol" when trying to connect with the same password. The encryption methods changed from one version to the next.

SET PASSWORD FOR 'some_user'@'some_host' = OLD_PASSWORD('newpwd');

Documentation [dev.mysql.com]

Hope this was on the right track . . .

Oliver Henniges

9:22 pm on Mar 11, 2009 (gmt 0)

Thank you very much, rocknbill, very much appreciated.

I'm quite busy at the moment and will take a closer look at your links after easter.