Forum Replies Created
-
AuthorPosts
-
ShadowMember
Even latin1 produced interesting side effects, byte length of field A was 10, while byte length of field B was only 5 after the INSERT statement on the first screenshot had been executed…
I guess, we won't be using MySql 5 beta for a while…
ShadowMemberI would not allow average users to get near of any SQLyog betas, but the idea is great!
ShadowMemberBut the most interesting results occured, when I switched to ucs2 encoding. Even the SELECT command should complete succesfully, but that USE command beats everything:
ShadowMember5, and 6 are not even released yet…
But here comes the first of the promised screenshots. Encoding was set to utf8 (table encoding is utf8 as well), and then we try to insert a new record. Field A is of int type (autoincrement), B and C are of varchar(45).
ShadowMemberUpon further testing, we are not sure, that this is a bug in SQLyog, it may well be in MySql itself… I'll be posting command line screenshots later on.
ShadowMemberWell, it's not just the lack of GUI support for stored procs that causes inconveniance, but INSERT/UPDATE commands fail to work if they involve special characters and client side encoding is set to utf8 using SET NAMES command. Encoding of underlying db or table(s) seems to be irrelevant to this issue. If the inserted/updated string contains special characters, an emtpy string gets inserted/updated.
This was tested with SQLyog Ent. v4.06 on W2K with MySql v5.0.3 beta, InnoDB. Special characters in question belong to Hungarian alphabet.
ShadowMemberNo, I did not mean sja-sample.xml! Sja uses XML files to store sync or notification jobs. Find the corresponding XML file (if the wizard had gone that far…) of you sync!
ShadowMemberPerhaps you could check the contents of generated XML file. SQLyog may write incorrect URL into that file.
ShadowMemberTry inceasing the connection timeout variables in case of the tunneled server!
ShadowMemberRight-click pop-up menu and hot-keys are not sufficient?
ShadowMemberFirst: not all table types (now referred to as engines) support relationships! Second: there is a separate relationship manager in SQLyog (F10 is its hotkey), use that one instead of manage indexes feature.
ShadowMemberThis is not a bug of SQLyog, but rather a bug of the GUI control SQLyog uses. It simply cannot handle line breaks… In case of SHOW CREATE TABLE command switch to Edit->Show results in text, and results will be displayed as expected. However, if you have more fields in the returned resultset, that contain line breaks, then even this workaround is spoiled.
ShadowMemberPing may not do Ritesh! 1. Some firewalls may be configured to drop all ICMP echo requests. 2. In case of tunneled connection, ping is not suitable either!
I suggest to use some common SQL command, such as “USE
” or “SHOW DATABASES”. ShadowMemberAs far as I can recall, SQLyog does store the settings in sqlyog.ini and this feature has long been requested. I tested on v4.06 and it works.
ShadowMemberJust forgot to attach the screenshot, and in edit mode I can't add picture to the post…
-
AuthorPosts