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

Forum Replies Created

Viewing 15 posts - 421 through 435 (of 642 total)
  • Author
    Posts
  • in reply to: Error No 1043 – Bad handshake #15306
    Shadow
    Member

    Apparently MySql considered the security changes so important that they broke compatibility. It wasn't the first in v4.1's history and that's why we are not upgrading yet.

    in reply to: drop constraint problem #15283
    Shadow
    Member

    I have already sent them an e-mail. It seems, however, that certain sessions create temp tables this way. If a session fails to create a temp table once because of this bug, then it won't stop. “Fortunately,” it is MySql 4.1-alpha. I wish, MySql released a beta (at least…)!

    in reply to: drop constraint problem #15281
    Shadow
    Member

    Well, not that great, we have an app that regularly creates temporary tables. What if it fails beacause of MySql creating temporary tables with illegal characters in their names?

    in reply to: foreign keys #15299
    Shadow
    Member

    All participating columns must have indices, not just the referenced ones!

    in reply to: Cant open file in SQLYOG #15291
    Shadow
    Member

    The index files are corrupt, try to repair the table by issuing a REAPAIR TABLE command. If that doesn't help, then dropping and recreating the indices may correct the problem.

    in reply to: drop constraint problem #15279
    Shadow
    Member

    I believe, I found the problem: MySql (not SQLyog) tried to create the temporary table's file with illegal character (“?”) in its name.

    in reply to: drop constraint problem #15278
    Shadow
    Member

    The create table command for the temporary table fails. It's getting more interesting as I manually executed the steps that SQLyog is supposed to do when dropping the table, and everything went smoothly. The drop constraint option, however, doesn't work even after repeated attempts. I will work on the issue tomorrow.

    in reply to: synchronizing tables #15160
    Shadow
    Member

    Great! 😀 We always use the same versions anyway…

    in reply to: Import from CSV file #15273
    Shadow
    Member

    In the my.cnf or my.ini (depending on which you have) net_read_timeout and net_write_timeout parameters (in seconds) should be increased or added. If the rows contain lots of data (blobs for example), then increasing the max_allowed_packet value may also resolve the issue. Furthermore, if you are using 4.0.15 and run it on Win platform, then you should upgrade because MySql screwd up the timeout settings…

    in reply to: synchronizing tables #15158
    Shadow
    Member

    SQLyog could issue a SELECT VERSION() command to both servers and warn the user of possible failures if the versions do not match!

    in reply to: Installer annoyance #15275
    Shadow
    Member

    At least it uninstalls rather neatly unlike other apps, only the personal folder needs manual removal if you have saved SQL statements.

    in reply to: HELP!!!!!! #15274
    Shadow
    Member

    Isn't it error 2002? If yes, then check out MySql manual's A.2.3 Can't connect to [local] MySQL server Error section.

    in reply to: Import from CSV file #15271
    Shadow
    Member

    You may try increasing the timeout value, so the import could complete.

    in reply to: a few bugs #15259
    Shadow
    Member

    1.: The SQL window is known to be buggy a bit, Ritesh promised to have it completely rewritten in SQLyog Max.

    2. and 3.: I haven't encountered any of the descibed problems on W2K. Ctrl+End works as expected. Unfortunately, it doesn't mean that these problems do not exists on WinXP… 😕

    in reply to: Novice wants to learn #15257
    Shadow
    Member

    And use SQLyog to manage your MySql dbs! 😀

Viewing 15 posts - 421 through 435 (of 642 total)