Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantOne Query tab and one Query Builder tab will be opened in every new connection.
We did not consider making this configurable! Is it so important?
ParticipantYes .. I would not rely on 4.1.7!!
and an add-on to my latest reply to vygi: it also could be the MySQL Server who has 'forgotten' the SET NAMES statement for the connection.
Participantdid you see this one?
http://www.webyog.com/forums//index.php?showtopic=3274
the questions taht we asked here you should answer too!
1) server version?
2) the returns of ” SHOW VARIABLES LIKE '%character%'; “
3) please dump a small table with such data, zip it and attch it here
Participantit is more likely that something has broken in Windows then, I think!
Internally SQLyog 6 stores strings in variables of type 'multibyte'. whenever communicating with the Windows API strings are transformed to a 'widechar' type. 'multibyte' is for storing utf8 characters, 'widechar' for ucs2/utf16. utf16 is the native Windows Unicode implementation.
The datatypes 'multibyte' and 'widechar' are basic C/C++ types and the library with all sorts of functions doing the transformation is a standard library too.
June 6, 2007 at 10:35 am in reply to: Keyboard Shortcuts (ctrl-m Etc) Disabled When Query Is Running #24119ParticipantThis is a bug in 6.0. It works with 5.32. We will fix that of course!
Participantthis was also how I understood. Just wanted to be perfectly sure.
Participantwe tried to build a small table here with the examples. It works here!
can you attach a small table (zipped .sql) and some example queries failing like this?
also execute ” SHOW VARIABLES like '%character%' ” and paste the result.
When SQLyog does “SET NAMES utf8” the server should handle everything – i.e. tranform between the charsets used for stored the data and the charset for the client and the connection! And we have not seen any situation where it does not!
How were data inserted? What happens if you insert data with SQLyog?
Participantplease tell – how do yo uexecute queries simultaneously? From different connection windows?
Participantyes .. SQLyog 6 can handle non-unicode data – or at least it should!
I still think your server is a 4.0 ?
ParticipantOK .. we will have to test more in depth too.
but repainting in the RESULT tab involves Win32 API calls. So I just wondered if it was Windows itself who 'waited'.
Participantthanks – still it would be very nice if you could create a very small table, dump, zip and attach. Plus give a few examples of queries failing!
But 4.1.7 is a very early version. There could very well be some issues with unicode in the parser.
Participant“but not possible to use queries which selects rows with 'like' statement and international characters. And for those queries I MUST use cp1251.”
NOOOOOOOOO! It will never work with 'set names' otherwise than 'set names = utf8' in SQLyog 6. Instead of guessing like that you should give a test case for reproducing your problem!
“but I suppose that SQLYog not convert data from sql-editor to utf8 and send it as is”
You should not 'suppose' either! You can ask!
SQLyog does not do any such thing! The server does – or should do – it all and that is the whole idea!
-all sorts OF COMMUNICATION between SQLyog and MySQL is – or should be – in utf8 with SQLyog6.
“When there is only international characters in the query – everything ok, but when I want to select 'cyrillc' data and use
or Could you explain the difference between 'international and 'cyrillic characters?
Please create a small sample table with cyrillic characters, export it, zip and attach here. Plus give a few example queries failing.
That will give us a chance to reproduce and understand.
Also answer: What is your MySQL version?
Finally I will repeat. YOU SHALL NEVER 'SET NAMES' YOURSELF WITH SQLYOG 6 !!!
Participant“How do I execute a stored procedure in 6.0?”
as always: you call() it. But I think you mean: how do I execute a create/alter PROCEDURE statement?
ParticipantFor historical reasons the 'common' query tab an the 'advanced' or 'special' query tabs for MySQL objects have a little different functionality.
The 'common' one supports 'execute (single statement)' and 'execute all'. the 'special tab type only the last one.
The historical reason is that when 5.0 was introduced the tokenizer code of the editor would not handle DELIMITER properly. That is history and I personally think we should remove the 'special' tab type. The 'common' one handles everything now.
The answer is that from a 'special ' tab you can 'execute all' (double arrow icon). Or you can copy the statement to a 'common' tab.
Actually in early 5.0 the 'execute' was greyed out too, but became 'greened in' again in later 5.x builds. By mistake I think! It always 'executed all'.
ParticipantYou simply shall not 'set names cp1251;' with SQLyog 6.0
It is designed to always use utf8 on the client side. It sends 'set names utf8;' (with MySQL servers that support 'set names') when it connects.
You shall not be worried that one character set is used on the server side and another on the client side! That is basically what the 'set names' command is for! The server transforms the encoding between the charsets used on the server and the client when sending and recieving data !
-
AuthorPosts
