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

Table Diagnostic

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Table Diagnostic

  • This topic is empty.
Viewing 10 reply threads
  • Author
    Posts
    • February 6, 2003 at 3:05 pm #7667
      shadaddy
      Member

      I just recently updated mysql from version 3.23.51 to 4.0.10. I opened up SQLyog and tried to do a table diagnostic and received the following error:

      Error No. 1064

      You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the

      right syntax to use near 'type=Extended' at line 1.

    • February 6, 2003 at 3:54 pm #13662
      CalEvans
      Member

      Did the History window show the actual query being issued? If so, please post it so we can see it.

      =C=

    • February 6, 2003 at 4:24 pm #13663
      shadaddy
      Member

      History window for table diagnostic type=extended

      [10:19:56 AM][ 0 ms] show tables from `Carbon`

      [10:19:59 AM][ 0 ms] check table `Carbon`.`vibratortable`, `Carbon`.`sodiumfractionstable`, `Carbon`.`sodiumbuttcrushertable`, `Carbon`.`rejecttable`, `Carbon`.`pittable`, `Carbon`.`pitchtable`, `Carbon`.`passgen`, `Carbon`.`oxytable`, `Carbon`.`liquidgraphitetable`, `Carbon`.`grndaystable`, `Carbon`.`greensievetable`, `Carbon`.`greendensitytable`, `Carbon`.`greendensityentrytable`, `Carbon`.`gascontable`, `Carbon`.`fluehistorytable`, `Carbon`.`fluehistoryinttable`, `Carbon`.`fluehistoryexttable`, `Carbon`.`fluehistory_fluhis`, `Carbon`.`fluehistory_flueint`, `Carbon`.`fluehistory_flueext`, `Carbon`.`coretechtable`, `Carbon`.`coredataentrytable`, `Carbon`.`castirontable`, `Carbon`.`carriertable`, `Carbon`.`butttable`, `Carbon`.`bakedscrapentrytable`, `Carbon`.`bakedensitytable`, `Carbon`.`bakedensityentrytable`, `Carbon`.`anod_hdl_table` type=Extended

    • February 6, 2003 at 6:01 pm #13667
      shadaddy
      Member
      CalEvans wrote on Feb 6 2003, 07:16 PM:
      Can you paste the check statement into the mysql command line tool on the server? Does it work?

      Can you cehck 1 or 2 tables instead of all of them? Does it work?

      =C=

      Tried pasting into the command line tool. Same error.

      Tried just one table. Same error.

    • February 6, 2003 at 6:23 pm #13664
      CalEvans
      Member

      What's your tabletype?

    • February 6, 2003 at 6:31 pm #13668
      Ritesh
      Member

      I have forwarded it to the development team and they are working on it. Probably we will come out with a solution soon.

      It will be very helpful, if you write the SQL yourself instead of using the GUI of SQLyog. If your table diagnostic SQL works then check out the difference between your Query and the one generated by SQLyog.

    • February 6, 2003 at 7:03 pm #13665
      shadaddy
      Member

      All tables are MyISAM. This problem did not occurr until I upgraded MySQL.

    • February 6, 2003 at 7:16 pm #13666
      CalEvans
      Member

      Dunno.

      The 4.0.10 manual does not list any changes to check table. type=extended is still listed as a valid command.

      2 more things to check.

      Can you paste the check statement into the mysql command line tool on the server? Does it work?

      Can you cehck 1 or 2 tables instead of all of them? Does it work?

      =C=

    • February 6, 2003 at 8:23 pm #13670
      Ritesh
      Member

      Seems, the working of some SQL commands has changed in MySQL 4.01 😉

    • February 6, 2003 at 8:39 pm #13669
      shadaddy
      Member

      Thanks for all the help. Just as a final note, I ran the following query from yog:

      check table `Carbon`.`vibratortable` extended

      And that worked. Also tried it from php. Seemed to work there as well.

      But still the built in tools, table diagnostics, check {none,quick,fast,medium,extended,changed} did not work.

    • February 6, 2003 at 8:51 pm #13671
      shadaddy
      Member

      Seems that way. Hopefully that's the only command that has changed. I've been messing around with it all day and that's the only thing I've noticed so far. Again thanks for the help, and I look forward to the fix on the GUI.

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