Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantNow I just enabled THAI on my (Danish) Windows and got those THAI fonts installed: LiLyUPC, KodchiangUPC, JasmineUPC, IrisUPC, FreesiaUPC, DilenialUPC and CordiaUPC
Using one of those I can actually enter some Thai characters (that become mapped to the non-ASCII characters (accented latin based character) available on my keyboard).
peterlaursen
ParticipantThis is the status regarding character set support in SQLyog:
http://webyog.com/faq/34_102_en.html
And here I studied details about TIS620 (of which I knew nothing!).
http://www.google.com/search?client=opera&…=utf-8&oe=utf-8
It is a 8-bit extended ASCII character set, I see, so there are chances.
1) First of all you should get SQLyog 5.11 or 5.12 beta. Charset support is better here than in 5.02 and you have the option to specify TIS620 as the character set for the connection
2) Next you should configure Windows to use THAI as the default language for non-unicode programs. You do so from Control Panel .. localised settings .. last TAB. This step is necessary to enable a Thai keyboard with non-unicode programs. But as you are Thai (and maybe use a Thai localized Windows) this may be OK the way it is.
3) From tools .. preferences you should choose a font that supports THAI writing for DATA PANE and the EDITOR.
(Actually step 3) may be sufficient to display data – also with 5.02 version, but I suggest you try 5.1.x )
Could you try this and report back any problems? I am very interested to hear if the SQL-editor will let you write Thai writing in comments for instance. I know that the Mozilla people and the OpenOffice people have had quite a lot of problems with Thai (should be an issue with half-size spaces as I understand it – but I don't claim to understand it!) , and I cannot guarantee anything.
There is a known issue with the HISTORY and OBJECTS tabs and such character sets – they support only the latin1 extension to ASCII. It will be fixed in version 5.2. Are you interested in testing 5.2 BETAS when they become available?
I would like to see a couple of screenshots of it working!
peterlaursen
ParticipantThe format of the XML-file has changed as there is now a
tag available. This could be the reason. Did you consider this?
I think you can open the XML file from the wizard and step through it an. Or simply add it manually like:
localhost ***** ***** 3306 [default] s and similar for target.
the [default] should work without no problems if charset defaults are the same on both servers. However if you have accented (non-ASCII)characters and servers uses different defaults (uft8 and latin1 for instance) you can specify [latin1] for both connections and data will still sync coreectly.
April 24, 2006 at 8:37 pm in reply to: Sqlyog 5.11 Could Not Start Application – Buffer Overrun #21336peterlaursen
ParticipantQuote:the two machines, where it is not possible to start application, has php 5.1.2 …and this one has a libmysql.dll of its own. I am not sure about this but maybe the Nullsoft installer has problems with the registry on some systems?
peterlaursen
ParticipantWell there are plans for a Visual SQL builder. I think that will do the trick …
peterlaursen
ParticipantWe have allready another report where it did not. So on some systems it does and others it does not.
But people having this isuue could try both .. until the thing is finally fixed.
April 24, 2006 at 6:17 pm in reply to: Sqlyog 5.11 Could Not Start Application – Buffer Overrun #21334peterlaursen
Participant@Ritesh .. check ticket 228 🙁
April 24, 2006 at 6:11 pm in reply to: Sqlyog 5.11 Could Not Start Application – Buffer Overrun #21332peterlaursen
ParticipantStay tuned …
You can expect an announcement is this Forum for 5.12 in a very short time. It links the client API statically, and w believe that solves the issue .
libmysql.dll
I think I have 15 copies of that file in different versions – a lot of program with MySQL client capabilities use it. But 5.12 will not use it as the code will be compiled into the sqlyog executable.
April 24, 2006 at 5:26 pm in reply to: Sqlyog 5.11 Could Not Start Application – Buffer Overrun #21330peterlaursen
ParticipantVery constructive input .. thanks!
In a graphical view it looks like this.
But same thing with 5.01 and 5.1, so I am not sure that that is it …
peterlaursen
ParticipantWe have similar reports and are working on it as a high-priority issue. Stay tuned!
peterlaursen
ParticipantQuote:The latest SQLyog now needs manual reconnection when connection to the sever is lost and that is really annoying.I am not sure about details (hard to remember everything) – if there is a change or not. Ritesh must tell.
But I agree that when clicking an object in the object browser for instance it should attempt to reconnect. And maybe even try one or a few reconnects automatically when connection is lost. I think the tunneller does.
peterlaursen
ParticipantWith 5.11 FINAL I get (doing the same exercise)
Error Code : 2006
MySQL server has gone away
(0 ms taken)
and nothing more. Not the popup 'Connection was lost'. I'll have to reconnect maually.
peterlaursen
ParticipantConclusion is that there is an issue with the memory space where SQLyog saves the data from the ini-file.
I have reported problems when an ini-file get 'too old' or 'too messy'
Could be the reason for buffer issues too!
peterlaursen
ParticipantDid you replace the tunnelling file?
peterlaursen
ParticipantThere was a similar report with an early beta:
http://www.webyog.com/forums/index.php?sho…=buffer+overrun
It is very hard to tell what happens here as it is a rare issue. We could not reproduce. There may be a memory handling bug that only takes effect in very special situations/on very special systems.
You can install 5.11 to a different folder. Try that. And try closing down as many unneeded background processes as possible. Also try starting the program as the first thing after reboot.
What is your OS?
If there is an issue it shall be fixed, but we simply need more info to spot it then. You are using the free version, so it is not related to auto-complete. That is important to know.
BTW: I can assure you that the issue with CURRENT_TIMESTAMP is fixed:
-
AuthorPosts