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

Bug – Processlist -> "view Query" Does Not Show Complete

forums forums Monyog Monyog: Bugs / Feature Requests Bug – Processlist -> "view Query" Does Not Show Complete

Viewing 6 reply threads
  • Author
    Posts
    • #10579
      Anonymous
      Guest

      I send this query to the server

      Code:
      UPDATE `imp_items_data`
      SET `imp_items_data`.`condition`=(
      SELECT
      /*
      CASE `imp_items_temp`.`condition`
      WHEN “” THEN “Ref”
      WHEN “Cer” THEN “Ref”
      WHEN “Yes” THEN “Ref”
      WHEN “new” THEN “New”
      ELSE `imp_items_temp`.`condition`
      END
      */

      `inner_data_temp_joint`.`condition`

      FROM
      (select CASE `imp_items_temp`.`condition`
      WHEN “” THEN “Ref”
      WHEN “Cer” THEN “Ref”
      WHEN “Yes” THEN “Ref”
      WHEN “new” THEN “New”
      ELSE `imp_items_temp`.`condition`
      END
      FROM `imp_items_temp`
      left JOIN
      `imp_items_data`
      on
      `imp_items_temp`.`altkey`=`imp_items_data`.`altkey`
      — where
      — `imp_items_data`.`altkey`='1018'
      group by imp_items_data.item_id
      ORDER BY `imp_items_temp`.`qty_on_hand` DESC
      ) as `inner_data_temp_joint`

      )

      and on the processlist section, after I click on “View query” it only shows

      Code:
      UPDATE `imp_items_data`SET `imp_items_data`.`condition`

      *********************

      Also

      if the query includes the n (new line) character, the “View query” removes the new line and puts the text together (later causing errors if I copy form there and paste on the mysql client)

    • #25099
      peterlaursen
      Participant

      I am not sure, but I think those issues are caused by the MySQL server and not MONyog.

      What is returned from the server if you manually issue 'SHOW FULL PROCESSLIST' ?

    • #25100
      Anonymous
      Guest
      peterlaursen wrote on Oct 10 2007, 04:45 AM:
      I am not sure, but I think those issues are caused by the MySQL server and not MONyog.

      What is returned from the server if you manually issue 'SHOW FULL PROCESSLIST' ?

      MySQL server gives back the full query, this is the output I got

      Code:
      mysql> show full processlistG
      *************************** 1. row ***************************
      Id: 2
      User: root
      Host: localhost
      db: tools
      Command: Query
      Time: 0
      State: NULL
      Info: show full processlist
      *************************** 2. row ***************************
      Id: 3
      User: root
      Host: localhost
      db: tools
      Command: Sleep
      Time: 52
      State:
      Info: NULL
      *************************** 3. row ***************************
      Id: 4
      User: root
      Host: localhost
      db: tools
      Command: Query
      Time: 27
      State: Copying to tmp table
      Info: UPDATE `imp_items_data`
      SET `imp_items_data`.`condition`=(
      SELECT
      /*
      CASE `imp_items_temp`.`condition`
      WHEN “” THEN “Ref”
      WHEN “Cer” THEN “Ref”
      WHEN “Yes” THEN “Ref”
      WHEN “new” THEN “New”
      ELSE `imp_items_temp`.`condition`
      END
      */

      `inner_data_temp_joint`.`condition`

      FROM
      (select CASE `imp_items_temp`.`condition`
      WHEN “” THEN “Ref”
      WHEN “Cer” THEN “Ref”
      WHEN “Yes” THEN “Ref”
      WHEN “new” THEN “New”
      ELSE `imp_items_temp`.`condition`
      END
      FROM `imp_items_temp`
      left JOIN
      `imp_items_data`
      on
      `imp_items_temp`.`altkey`=`imp_items_data`.`altkey`
      — where
      — `imp_items_data`.`altkey`='1018'
      group by imp_items_data.item_id
      ORDER BY `imp_items_temp`.`qty_on_hand` DESC
      ) as `inner_data_temp_joint`

      )
      3 rows in set (0.00 sec)

      mysql>

      and if I did not use the G option:

      Code:
      mysql> show full processlist;
      +—-+——+———–+——-+———+——+———————-+————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————-+
      | Id | User | Host | db | Command | Time | State | Info |
      +—-+——+———–+——-+———+——+———————-+————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————-+
      | 2 | root | localhost | tools | Query | 0 | NULL | show full processlist |
      | 3 | root | localhost | tools | Sleep | 47 | | NULL |
      | 4 | root | localhost | tools | Query | 22 | Copying to tmp table | UPDATE `imp_items_data`
      SET `imp_items_data`.`condition`=(
      SELECT
      /*
      CASE `imp_items_temp`.`condition`
      WHEN “” THEN “Ref”
      WHEN “Cer” THEN “Ref”
      WHEN “Yes” THEN “Ref”
      WHEN “new” THEN “New”
      ELSE `imp_items_temp`.`condition`
      END
      */

      `inner_data_temp_joint`.`condition`

      FROM
      (select CASE `imp_items_temp`.`condition`
      WHEN “” THEN “Ref”
      WHEN “Cer” THEN “Ref”
      WHEN “Yes” THEN “Ref”
      WHEN “new” THEN “New”
      ELSE `imp_items_temp`.`condition`
      END
      FROM `imp_items_temp`
      left JOIN
      `imp_items_data`
      on
      `imp_items_temp`.`altkey`=`imp_items_data`.`altkey`
      — where
      — `imp_items_data`.`altkey`='1018'
      group by imp_items_data.item_id
      ORDER BY `imp_items_temp`.`qty_on_hand` DESC
      ) as `inner_data_temp_joint`

      ) |
      +—-+——+———–+——-+———+——+———————-+————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————-+
      3 rows in set (0.00 sec)

      Both cases gave me the full query.

      Thanks for looking into it.

    • #25101
      peterlaursen
      Participant

      I will ask the MONyog team to look into it!

    • #25102
      peterlaursen
      Participant

      yes .. issue confirmed.

      This happens basically because of HTML formatting.

      I hope that on Monday or Tuesday we can have 'architected' the fix and give an estimate of how much time it will take to implement.

    • #25103
      Anonymous
      Guest
      peterlaursen wrote on Oct 12 2007, 08:39 AM:
      yes .. issue confirmed.

      This happens basically because of HTML formatting.

      I hope that on Monday or Tuesday we can have 'architected' the fix and give an estimate of how much time it will take to implement.

      Alright, I look forward to seeing the fix implemented.

      Thanks!

    • #25104
      Rohit
      Member

      Fixed in MONyog 1.11

Viewing 6 reply threads
  • You must be logged in to reply to this topic.