Forum Replies Created
-
AuthorPosts
-
Ritesh
Memberpeterlaursen wrote on Apr 3 2006, 04:39 PM:There is no problem other than his computer had 'dropped' the service. That happens on Windows. A reboot fixed it.Even if the OS dropped the i.e. the MySQL is not running, SQLyog should throw a “Cant connect error”. It should not hang.
Also, the MySQL command line tool is able to connect without any problem. The command line and SQLyog both uses C client library to connect to the server. Only difference being the client library version.
MemberWhich MySQL version and are you using tunneling? Maybe, its a problem with the client API.
MemberBug fixed.
It was introduced in v5.1 BETA 4 when we changed the HTTP implementation.
MemberAdded for v5.2.
MemberYog is not a person but can be classified as Karma or deed. Yog is described as unflinching concentration towards your target without bothering about intermediate results. That's what we stand for. To make the best products in its category!
@nicmar: Thanks for your encouraging words. Be assured that 5.1 will not be released till all the known bugs (reported by you and other people) are fixed.MemberMore food for thought for v5.2.
MemberThanks nicmar for the detailed report. We will work on it tomorrow (even though its a saturday) and fix it. We plan to release 5.1 RC on wednesday. This will have this bug fixed.
MemberThis is a known and a design issue. You will need to be in the same database context as the table is.
MemberThat is exactly what I am trying to say here. Even if one byte data is mapped to utf8, it will not be displayed correctly as the codepoint between latin charsets and utf8 is different. We are not supporting that as of now. You will need to select latin1 in the connection manager.
MemberI will check upon it today and if its a bug, will be fixed for RC1, which we plan to release by next Wednesday.
MemberInteresting that code doesn't work. Did you use the new code as the registration code method changed between 4.x to 5.x.
One license means that one copy of SQLyog can be installed on one computer. Multiple people using the same machine can use it though without purchasing another license.
Memberpeterlaursen wrote on Mar 29 2006, 07:12 AM:SCHEDULED BATCH EXPORT WIZARDThat is a new name isn't it? :huh:
And what about the 'ordinary' export tool then? 'As is' with MySQL 3-4.0 and uft8 with MySQL 4.1++?
That was my point too!
I meant Powertools -> Scheduled Backups 😀
Ordinary export will not have this option. It will export with utf8 for versions > 4.1 and normal when versions < 4.1. We dont plan to add any new features in the normal export. All the new improvements will be done in Powertools -> Scheduled Backup.
peterlaursen wrote on Mar 29 2006, 07:25 AM:And I suppose that thespecified wil be used for Code:set character_set_results =and only that? Just like SQLyog beta4 does?
Now that would actually allow for syncing data between databases having different charset with MySQL 4.1++ when specifying
, as the SJA would use utf8 internally and the server would convert charset when storing data as described in defaults or columnn-definitions. Am I right?
Not in BETA 4. We have still not finalised the design regarding this as of now.
MemberThanks for the bug report. Fixed in BETA 5 development team.
Memberpeterlaursen wrote on Mar 29 2006, 07:28 AM:@riteshdid you consider this discussion in relation to BETA 5 ?
Yes indeed. Previously, we were leaving out couple of charsets but from BETA 5, everything will be in the drop down. Display of the data though will depends whether it is single byte or multibyte. We plan to support display of data which is stored in utf8 but are of one byte in BETA 6. Right now, you cannot display data with utf8 charset even though it contains one byte data.
Quote:You must also explain how to use the charset selector in connections manager!I will update the docs as soon as I can.
MemberInteresting request. I will discuss it with my developers now and update this thread in sometime.
-
AuthorPosts
