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

SQLyog and MySQL5.0

forums › forums › SQLyog › Using SQLyog › SQLyog and MySQL5.0

  • This topic is empty.
Viewing 7 reply threads
  • Author
    Posts
    • February 9, 2005 at 11:23 pm #8791
      TylaG
      Member

      The most recent version of SQLyog (downloaded 9 Feb 2005) is not compatible with MySQL 5.0.2-alpha. While tables can be created, clicking on the table name within SQLyog crashes MySQL though SQLyog still runs, eventually doing a time out. Not a biggie, MySQL is stil in alpha, but FYI. Server environment: Win98SE / MySQL 5.0.2-alpha; Client environment: Win XP SP2

      Tyla

    • February 10, 2005 at 3:05 am #16999
      Ritesh
      Member

      Have you executed the same query from the MySQL command line tool?

      I believe its a bug with MySQL as under no circumstances should MySQL server crash.

    • February 10, 2005 at 3:55 am #17000
      peterlaursen
      Participant

      CONFIRMED !

      With my setup the description of the error is truly correct with yog 4.0.2 + Mysql 5.0.2 both installede on a WinXP (Danish) SP2

      It works correctly with ver MySQL 4.1.9

      The yog 4.0.0 RC1 (that I staill have installed) does not show this behaviour – not with mysql 5.0.2 either.

      It is ONLY the combination {yog 4.0.2 + Mysql 5.0.2} that makes this happen. Not other comninations of yog a.

      Actually this is the first time I have been able to crash my mysql server !!!

      What would happen if it is a remote server, and not a local MySQL ?!?

      >> Ritesh

      THERE IS NO QUERY AT ALL –

      this is correct

      Quote:
      clicking on the table name within SQLyog crashes MySQL
    • February 10, 2005 at 3:56 am #17001
      peterlaursen
      Participant

      … just a correction

      It is ONLY the combination {yog 4.0.2 + Mysql 5.0.2} that makes this happen. Not other comninations of yog a.

      >>>

      It is ONLY the combination {yog 4.0.2 + Mysql 5.0.2} that makes this happen. Not other comninations of yog and MySQL.

    • February 10, 2005 at 6:06 am #17002
      Ritesh
      Member

      I have forwarded the issue to my development team.

      I will revert back soon.

    • February 10, 2005 at 6:15 am #17003
      peterlaursen
      Participant

      no, I now think that Ritesh was right in the first place.

      the sql-statement that causes mysql 5.0.2 to crash is

      Quote:
      describe `dbname`.`tablename`  

      – nothing else.

      Mysql 5.0.2 also crashes when issuing that statement from “MySQL Query Browser” from http://www.mysql.com

      I now also can reproduce it with yog 4.0.0 RC.

      So it undoubtedly is an issue wiht the 5.0.2 alpha.

      However it's somewhat confusing that it does not always happen …

      My serverversion is max-nt.

      I tried with and without “named pipes” and with and without debugging, but it makes no difference here.

    • February 10, 2005 at 11:57 am #17004
      Ritesh
      Member

      😀

      I guess I need to call up the MySQL developers.

    • February 10, 2005 at 12:06 pm #17005
      Ritesh
      Member

      Looks like this is a known bug and has already been fixed in 5.x development tree. The fix will be available in MySQL v5.0.3.

      Please check http://bugs.mysql.com/bug.php?id=6950 for more information.

  • Author
    Posts
Viewing 7 reply threads
  • You must be logged in to reply to this topic.