Re: [tlug] Charset and other problems with MySQL versions

[Shawn <bofh@example.com>]

Thanks Ed,

On Wed, Jul 20, 2005 at 01:32:46AM +0900, Edward Wright wrote:
> 
> You DO still have the old database, right? Why not try mysqldump of the
> data from there, and use that file to create the new database. Check the
> mysqldump man page for options... there are quite a few....  'tho if you
> are lucky you may not need them. I have had to edit the output of
> mysqldump occasionally to get it to import.

I do have the old database. I took your advice and copied the 4.1.12 data
back to the 3.23 (not 2.23 as I'd previously said) machine, imported to and
exported from the 3.23 install. I then moved the exported data to the 4.1.12
machine and tried:

# mysql -uroot -p PADB < warabi-PADB.sql

but get...

ERROR at line 3978: Unknown command '\''.

It seems like its tripping over a double-byte character. I went back into the
ports hierarchy, deinstalled mysql41-server, added
"--with-extra-charsets=complex" to the Makefile, and ran a "make install." I
tried to then import the .sql file again as above and got the same Error.

Any further suggestions?

> If you are using a precompiled binary from MySQL it should have been compiled
> with complex character sets, which should cover your Japanese encodings ok.
> If not, then you need to compile that support in.

Not sure if I put the right flag in the Makefile or if its something else I
need.

> All I can really recommend here is RTFM, and then again and then again until
> you start to figure out what they're talking about. Note there are two relevant
> sections: 5.9 and 10 (in the online docs). 

I'll keep reviewing...

> Another gotcha that drove me nuts (maybe you've already passed it) was that
> password hashing changed with 4.1.x. Relevant section of the docs is
> 5.6.9. Password Hashing in MySQL 4.1

Yes - got that one a couple of days ago. Had me stumped for a bit.

Thanks - if anyone else knows what configuration option I'm missing, any
advice would be appreciated.

Shawn