> Well, they were generated by MySQL and I can open them with
> e.g. the Windows Editor Notepad. But I don't know if they are
> actually encoded in UNICODE.
> Since I can open the file with Notepad and read the
> statements, I assume, it is not UNICODE. They look just like
> in the email below.
Windows Notepad handles Unicode just fine, both UTF-16 (labeled Unicode
in notepad) and UTF-8 (labeled UTF-8).
To test, open the file in Notepad, then do "File->Save As". The
"Encoding" dropdown box will default to whatever Notepad detected when
it opened the file. If it's UTF-16 and you need UTF-8, just change the
encoding and save under a different name.
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
