[yogus]

peterlaursen wrote on Mar 27 2008, 07:50 PM:

@yogus

1) What is the program version that you are using? Unicode is supported from 6.0.

2) I asked you to read the FAQs. Did you? In particular this one:

http://webyog.com/faq/content/34/152/en/my…-in-sqlyog.html

3) Please attach a small example of such dump (SMALL and zipped, please!). It is better to do things than to talk about things!

4) “does sqlyog check which charset the .sql-import-files have?”

both yes and no!

as regards yes YES: we detect the encoding of the file.

as regards NO: SQL imports are started in a seperate connection thread. Unlike for the GUI thread we do not SET NAMES for batch jobs, The script it self is supposed to! Does the script contain the statement “SET NAMES UT8” ?

more info: http://webyog.com/faq/content/34/148/en/do…y-language.html

alright, it was my mistake, sorry 🙂

my file does not contain “set names utf8;”.

i thought this is not necessary because i read parts of faq like “Do I need to SET NAMES to display characters of my language? => No, you won't. SQLyog does all what is required!”… 😉

what about a function which recognise utf8-files and automatically send “set names utf8” or whatever the encoding is to the server?

thanks

greets

[yogus]

hello,

i mean when i have an .sql-dump (chars are utf8-encoded) of a whole database.

when i create a new db in sqlyog and do an import of the .sqlfile by “Restore from SQL-Dump…” it does not work with utf8-files.

it works by converting the dump to iso-8859-1 with the program iconv.

does sqlyog check which charset the .sql-import-files have?

greets

[yogus]

peterlaursen wrote on Sep 7 2007, 02:49 PM:

I am sorry for not informing you!

The fix will be included in 6.1.

When we export we use utf8-encoding.

Basically we will need to specify the charset with the LOAD DATA INFILE statement to be sure that it always import correctly, no matter the server settings.

But there is an easy workaround, actually. Just open the file in Notepad .. save as .. explicitly select ANSI for the encoding. Now latin special characters will import.

when do you finally fix this bug? i think it's not fixed yet. (when i import an utf8 database-dumb with an “umlaut” (ä,ü,ö) it does not work correctly) ä => ä; ö => ö

please fix this bug, it's so annoying… 🙄

greets

you are doing a great job, thanks!!

[Author]

Posts