[Nick]

Just to let you know that 5.1 Beta 6 seems to have sorted all the issues out and I can now do Turkish perfectly both locally and via http tunnelling.

Thanks very much for working to fix the problems I was having.

Nick

[Nick]

😎 Glad I could help…

Nick

[Nick]

Hi Peter,

Let me try and answer your questions:

Quote:

test1.sql does not have character set definitions in the columns definition – test2.sql has.

But test1 has comments – test2 has not.

… Looks like two different tables / two different tries? Could you explain? How did you create test1.sql? With what program versions (MySQL and SQLyog)?

Yes, test1 and test2 were two different attempts. For both attempts I followed your instructions as close as possible using the sql you posted to create the table. For both attempts I think that I added rows by entering id values and then a mixture of typing in Turkish from the Keyboard and pasting in text from a Turkish website.

I am using mySQL 4.1.18 and SQLyog 5.1 beta 5

Btw I am also running an English Windows XP SP2 with 'English/UK' selected in the 'Regional options' tab, and 'Turkish' selected in the 'Language for non-unicode programs' in the 'Advanced' tab of the 'Regional and Language Options' in the Control Panel.

[attachment=424:attachment]

Quote:

If I use 'latin5' for the connection AND from 'preferences' choose Turkish script for the DATA/RESULT pane I can actually display it correctly. Most surprisingly I can enter rows with Danish characters æøå in all three columns – export and import again. And even the 'latin5' column does not garbage those characters. Are they mapped with the Türkish script too? @Nick – you know?

In tools, preferences, font I have Courier New 9px Turkish script for both SQL editor and data display.

Actually, Turkish characters seem to be handeled fine in the query window and in the table data view. The problems I had/or have is that 1. adding comments using the alter table converted turkish chars to question marks, although the Turkish chars in the comments were retained and 2. The fonts used in the comments and history pane don't render the Turkish correctly. [ooops SQLyog just crashed again as I was flicking between the tabs!]

Quote:

The 'script' settings in 'preferences' for font in the Editor do not work either. If I choose Turkish script and paste Nick's test2.sql into it, all the special Turkish accents are removed ('cedilla-s' becomes plain 's' etc.). This is not a display issue only because if I run the script from Editor pane characters without these accents are saved.

I don't have this problem, I think because as I mentioned above I have 'Turkish' set for non-unicode programs in the Control Panel.

Quote:

Can you execute SQL written with Turkish keybord settings and Turkish script setting in SQLyog correctly?

Yes, I can. That works ok.

[attachment=425:attachment]

Nick

What I forgot to menition is that when I did the ALTER TABLE in the first test, the 'character set utf8', 'character set ucs2' and 'character set latin5' elements were stripped out.

Compare attempt 1:

[attachment=426:attachment]

With attempt 2:

[attachment=427:attachment]

Both tables were created with the same SQL statement, with just the name of the table changed in the second attempt.

Code:

CREATE TABLE tt (id bigint, utftext CHAR(20) CHARACTER SET utf8, ucstext CHAR(20) CHARACTER SET ucs2, latintext CHAR(20) CHARACTER SET latin5);

The difference was I didn't add comments to the second attempt.

Nick

[Nick]

I've been having similar problems with beta5 (I was having them with beta4 too).

SQLyog just dissapears randomly when I'm doing stuff with the Table View tab.

I have been reporting this is another thread.

it's happened with large tables and small tables. Usually a mixture of clicking in and out of fields, on the various field headers to sort the table, on the show all tickbox, and back and forth from the table list is enough to produce the crash.

Nick

[Nick]

Hi Peter,

I did as requested but I had some problems along the way. I was using the beta 5 which I downloaded earlier today.

1. SQLyog crashed a few times while clicking in the date table view.

2. When entering Turkish data into an array of 10 rows that I inserted by entering 10 unique ids after creating the table, some data that I subsequently entered, disappeared. This happened on entering the refresh button after I had been pasting snippets of Turkish texts into different fields.

3. After entering text into the table, I tried to add some table and column comments using the alter table function. After I clicked on the alter table button the columns with converted to latin1_sweedish collation (see fig1.gif) and all the Turkish characters in each of the three columns turned to question marks (see fig2.gif). The comments I added were retained as the correct character although are not displaying properly in the Objects tab:

i.e. the comments below are correct:

Field Type Collation Null Key Default Extra Privileges Comment

---

---

---

---

---

---

---

---

---

id bigint(20) NULL YES (NULL) select,insert,update,references ııIIiiİİşşŞğğĞĞ

utftext char(20) latin1_swedish_ci YES (NULL) select,insert,update,references ğğşşİİ

ucstext char(20) latin1_swedish_ci YES (NULL) select,insert,update,references ğğŞŞİİ

latintext char(20) latin1_swedish_ci YES (NULL) select,insert,update,references ğğİİİŞŞİ

but the attached screenshot shows the comments displayed incorrectly (see fig1.gif) and test1.sql shows the comments outputting ok.

[attachment=414:attachment]

[attachment=415:attachment]

4. I couldn't find any reference to the utf8-option mentioned in the last post, so I just exported a second attempt using the “Export table using SQL statements” option.

This seemed to export ok. See fig3.gif for how the table looks in sqlyog, and the test2.sql for the resulted export.

[attachment=416:attachment]

Hope that is helpful, please get back to me if you want me to do other tests.

Nick

test1.sql and test2.sql attached as zip

[Nick]

Ritesh wrote on Mar 28 2006, 11:38 AM:

BTW, I would like to offer you a FREE license for all the help that you provided regarding SQLyog.

Wow, thank you very much 😀

Nick

[Nick]

Hi again,

Just to let you know that I got the SQLyog to crash on a non Turkish DB:

1. Connect to DB (the one in question has around 100 tables)

2. click on the “3 table data” tab

3. Expand the tree view to show all the tables

4. click on the first table

5. now use the up and down arrow keys (a key press at a time or holding down the key till it auto-repeats) to move up and down the list of tables (the table data shows the first 50 rows of each table as the table name on the right is highlighted)

Within a short while the program crashes.

Hope that is helpful to identify the problem in this beta.

Nick

[Nick]

p.s. I send some test data to Ritesh direct by email,

Nick

[Nick]

Still getting the ILLEGAL COLLATION error with mySQL 4.1.18

Nick

[Nick]

Hi,

I managed to work out how to get the crash every time:

1. Connect to any database

2. Navigate to a table in the tree veiw

3. Click on the 3 Table Data tab

4. click into a any field of the new record at the bottom of the table view

5. type some text but don't press return

6. click directly on the header bar at the top of that column to initiate a sort

SQLyog dissapears for me more or less everytime what ever db I use and whereever I connect to. Sometimes I need to do steps 4-6 a few times.

Hope this helps

Nick

[Nick]

What were values become (NULL)…

I've tried to replicate the problem by everything seems to be ok at the mo…

NIck

[Nick]

A further anomaly,

I just ran a SELECT query on the table I've been editing and it NULLED out each field of about 5 of 30 records. Then after I tried to return to the table view, it quit/crashed with no error.

Again this was after the client and connection vars were set to latin5.

Nick

[Nick]

Hi Peter,

I still seem to be having some issues with SQLyog and Turkish. This time it is with SQLyog connecting normally to a local mysql on the same PC: mysql 4.1.16-nt & sqlyog 5.1 beta 4.

I connect to a latin5 database selecting latin5 in the new dropdown on the connection page and once connected if I run SHOW VARIABLES LIKE '%character%'; I get:

“character_set_client” “latin1”

“character_set_connection” “latin1”

“character_set_database” “latin5”

e”character_set_results” “latin5”

“character_set_server” “latin1”

“character_set_system” “utf8”

If I navigate to a table view and try and change any value in a text field, I get this error:

Error No 1267 – Illegal mix of collations (latin5_turkish_ci, IMPLICIT) and (latin1_sweedish_ci, COERCIBLE) for operation '='

After this error appears I am forced to quit the program as I cannot get the focus away from the record that I tried to edit.

I found though that before editting if I run either:

SET NAMES latin5

or

Set character_set_connection=latin5

Set character_set_client=latin5

before trying to make any changes I can edit without trouble. After running either of these queries I get the following from SHOW VARIABLES LIKE '%character%';

“character_set_client” “latin5”

“character_set_connection” “latin5”

“character_set_database” “latin5”

“character_set_results” “latin5”

“character_set_server” “latin1”

“character_set_system” “utf8”

Also, I have also had trouble when clicking on the header bar at the top of the table view to sort the table. Sometimes it's ok, sometimes the program just crashes/quits without an error. I don't seem to be able to replicate any pattern. Though I think it may have always been after setting the client and connection vars to latin5.

Once more, any help would be appriciated.

Thanks in advance for your help.

Nick Mott

[Nick]

peterlaursen wrote on Mar 20 2006, 06:08 PM:

Could you try with Turkish?

That works perfect 🙂

Great job!!

Nick

[Nick]

Quote:

I do not understand why the SET NAMES returns a Server Error from SQLyog if it works from PHP.

Me neither… But on my local server if I don't run the SET NAMES command I get

Yarat?l??

M?s?r'dan Ç?k??

…

instead of

Yaratılış

Mısır'dan Çıkış

…

(I know that I could set the default character set to latin 5 of course…)

Also, I can confirm that I too can read the Turkish ok but it is only when I am trying to write that I have a problem, either running a command in the query window, by editing in the table view or by trying to transfer the the table from my local DB to the online DB…

Nick

[Author]

Posts