Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 15 posts - 2,776 through 2,790 (of 7,398 total)
  • Author
    Posts
  • in reply to: #27128
    peterlaursen
    Participant

    Are you talking about compressing backups?

    We do not have compression in our backup tools. However you may use a workaround like described here:

    http://webyog.com/faq/content/24/117/en/ca…ja-backups.html

    (Filzip and 7zip and probably more compression tools are usable)

    in reply to: #27125
    peterlaursen
    Participant

    Another possibility is that a firewall blocks the port.

    Did you try using HTTP-tunnel (take the Enterprise TRIAL for testing)?

    Basically only your webhost personnel can tell you all those details.

    But please read in program help about tunnelling and also read:

    http://webyog.com/faq/content/23/17/en/err…erver-host.html

    in reply to: #27123
    peterlaursen
    Participant

    First try just 'perfora.net' as host if that is where you mysql server is! where does '*.' come from? Did you enter this yourself?

    You may also need to use a name server alias for the mysql server like 'mydb.perfora.net' or 'mysql.perfora.net' Please refer to:

    http://webyog.com/faq/content/16/66/en/wha…-at-an-isp.html

    (only your ISP/Sysadmin can tell you the name server alias if it is not available from your account information or control panel)

    in reply to: #27107
    peterlaursen
    Participant

    strange .. we have not changed (at least not on purpose) that is related to all what we discussed here.

    It may be a compiler issue. I think we should consider moving to a more recent Visual Studio version for building SQLyog. We still use VS 2003 and maybe there is a Vista compability issue. That is the only idea I have!

    in reply to: #27113
    peterlaursen
    Participant

    additionally .. if you use the 'scheduled backup powertool' (ENTERPRISE version only) there is an option to generate a file for every table.

    in reply to: Show Table Data In Text #23513
    peterlaursen
    Participant

    There is a setting in 'preferences' like 'open tables as default'.

    We are cautious to save the grid/text setting/preference. It could confuse users who enable 'text' by mistake. Anyway we will discuss this.

    in reply to: #27105
    peterlaursen
    Participant

    Thank you. There was good information here that we may be able to use. Nobody here thought about the 'run as administrator' option!

    One more question: do you have 'user account control' (UAC) turned ON?

    (a google link

    http://www.google.com/search?client=opera&…-8&oe=utf-8

    .. with different related info.)

    1) Could you try to turn UAC OFF?

    2) Would you mind try installing 7.1 beta1 just released today and try this? (you can have both installed to different folders and they will use the same settings).

    in reply to: #27054
    peterlaursen
    Participant

    Please see: http://www.webyog.com/blog/2008/08/12/sqly…-been-released/

    Quote:
    * Program dialogues for schema sync, create/alter table, manage indexes (including sub-dialogues) and manage foreign keys (including sub-dialogues) are now resizable.
    in reply to: Show Table Data In Text #23511
    peterlaursen
    Participant

    We have now started the release process for 7.1 beta1.

    Release notes tell (among others):

    Quote:
    * 'show in text' (Ctrl+L) is now functional for both DATA tab and RESULT tab.

    In 10-15 minutes you should be able to download it!

    in reply to: #27109
    peterlaursen
    Participant

    I think it is the same issue as reported recently by another user. This record in our issue tracker summarizes:

    http://code.google.com/p/sqlyog/issues/detail?id=827

    SQLyog does not *realize* that connection is lost. It cannot as there is not continuous cummunicataion between a MySQL server and a client. SQLyog will reconnect however, when it receives 'server gone away' error or 'cant connect' error. That is current implementation. And was like this from very early in SQLyog development.

    In 7.02 reconnects and reconnect attempts are logged to HISTORY. This was added to provide debugging info for such situation. Please check if there are any such records there.

    In those rare situations where reconnect is very slow the only solution would be to keep the connection *artificially* alive with mysql_ping() as described.

    This “If after 15 minutes of inactivity, I first disable and then reenable my wireless network before attempting to return to using SQLyog, the hanging problem does not occur.” i think tells that the slowness with reconnection is caused by your wireless system/router! Probably some internal cache/buffer not working optimally.

    Anyway please tell (from HISTORY tab) if you see reconnects or reconnect attempts after this has occured. It will also give time-related information.

    in reply to: #27103
    peterlaursen
    Participant

    I can tell that I have experienced this myself. But this is not introduced in 7.02. I had it randomly in late 6.x versions too. And sometimes it was Query Builder tab that hang. As told it happens randomly. I may not see it for weeks .. but then it may occur again. After a reboot it will normally not continue like that.

    Also it has only happened with (HTTP or SSH tunnelling) connection to remote servers with a rather bad connection. I have reported that internally, but not reproducable from our Bangalore office. One test engineer told me though that he saw it a few times.

    It has only been seen on Vista. Basically I think it is an issue with the network layer in Vista.

    Maybe it is also related to 'data execution prevention' (that is far from perferct): problems with it reported here for instance:

    http://www.techsupportforum.com/microsoft-…-odd-issue.html

    If can can 'work around' it we will of course. But we need to reproduce it consistently or understand the reason for it better. So if you can tell some more 'systematics' than what I coud find it would be helpful.

    You could also read this:

    http://www.labnol.org/software/tutorials/w…ors-crash/2856/

    Does the performance monitor have records of such 'program instability' for SQLyog and other programs on your system?

    One final idea is that the I/O caused by autocomplete may also be involved in this. You can try

    1) disable autocomplete

    2) if that worked rename the TAGS folder. A new one will be built.

    in reply to: #27101
    peterlaursen
    Participant

    Do you execute an external file that is also open in SQLyog editor? That is how I understand what you are telling. If not like this, please explain more in detail (step-by-step how to reproduce).

    in reply to: #27097
    peterlaursen
    Participant

    Issue confirmed! The error comes with sync 4.0<>5.0 in either direction. Only a single (even identical) row needs to be present in both tables to reproduce this. Syncing 5.0<>5.0 works fine!

    I tried to drop the FLOAT and DATETIME columns (the ones that one should suspect could cause cross-version trouble), but that was not enough! I will not go deeper tonight. The team will debug on Monday.

    test case:

    ********

    CREATE TABLE for 5.0:

    CREATE TABLE `fx_audusd` (

    `datetime` char(18) collate latin1_general_ci default NULL,

    `value` char(17) collate latin1_general_ci default NULL,

    `diff2prev` float NOT NULL default '0',

    `datumzeit` datetime NOT NULL default '0000-00-00 00:00:00',

    `file_id` datetime NOT NULL default '0000-00-00 00:00:00',

    `timekey` smallint(3) NOT NULL default '0',

    `fxid` int(11) NOT NULL auto_increment,

    `fxstatus` tinyint(2) NOT NULL default '0',

    PRIMARY KEY (`fxid`),

    KEY `fxid` (`fxid`)

    ) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;

    CREATE TABLE for 4.0 — assumed server charset is latin1

    CREATE TABLE `fx_audusd` (

    `datetime` char(18) default NULL,

    `value` char(17) default NULL,

    `diff2prev` float NOT NULL default '0',

    `datumzeit` datetime NOT NULL default '0000-00-00 00:00:00',

    `file_id` datetime NOT NULL default '0000-00-00 00:00:00',

    `timekey` smallint(3) NOT NULL default '0',

    `fxid` int(11) NOT NULL auto_increment,

    `fxstatus` tinyint(2) NOT NULL default '0',

    PRIMARY KEY (`fxid`),

    KEY `fxid` (`fxid`)

    ) TYPE=MyISAM

    DATA for both:

    insert into `fx_audusd`(`datetime`,`value`,`diff2prev`,`datumzeit`,`file_id`,`timekey`,`fxid`,`fxstatus`) values ('20081212121212',NULL,3434,'2008-12-12 12:12:13','2008-12-12 12:12:12',11,2323,11);

    .. next run the sync between the two and the error occurs as described by user!

    But one hint though to reporter: this

    PRIMARY KEY (`fxid`),

    KEY `fxid` (`fxid`)

    defines an ordinary key defined identically to the PK. This

    PRIMARY KEY (`fxid`),

    should be enough. Two identical keys like this costs additional diskspace and performance on the table!

    in reply to: #27087
    peterlaursen
    Participant

    Just a follow-up. The issue was a port conflict on port 5555. Specifying a port not in use solved the issue.

    As regards the documention request: The documentation that ships with MONyog is 'tailored' for the MONyog javascript engine. It will not work with standard webservers 'out of the box'. I do not think either that most of the documentation is interesting if there is no running MONyog instance as a reference. However we will discuss how to make the part of the documentation that describes the installation process and requirements for installation available for users before and during installation.

    in reply to: #27095
    peterlaursen
    Participant

    I think this should be enough for debugging this issue.

    SJA will not need 'shadow copies'. It will also run from anywhere but two problems could arise

    1) If SJA.EXE is not where SQLyog.EXE is then starting SJA from the wizard will fail

    2) If PLINK.EXE is not where SJA.EXE is then SSH-tunnelling will fail

Viewing 15 posts - 2,776 through 2,790 (of 7,398 total)