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

"execute Selected Query" Malfunctions In "special" Edi

forums forums SQLyog SQLyog: Bugs / Feature Requests "execute Selected Query" Malfunctions In "special" Edi

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #12192
      TerryN
      Member

      Title continued: …Editor tab if earlier query invalid

      The behavior of “Execute selected query” (Ctrl-F9) differs depending on whether the current tab is a “special” one (e.g. stored procedure definition) to SQLyog or just a plain-old blank query tab. In the first type it behaves as “Execute current query” (F9) would.

      To reproduce:

      Right-click on Views in the object browser. Create View. Enter any name.

      Replace the new tab's contents with the following (excluding the lines):

      —-

      DELIMITER $$

      CREATE PROCEDURE test()

      BEGIN

      SELECT

      END$$

      DELIMITER ;

      SELECT 2;

      SELECT 3;

      —-

      Select “SELECT 2;” with the cursor.

      Right-click. Execute Query > Execute selected query.

      Notice that the results of three statements are shown.

      Behavior is the same for Create Function, Create Stored Procedure, Create Trigger, etc.

      In contrast, only the selected query is executed, as expected, if you do the above in a tab opened via File > New Query Editor.

    • #31668
      ashwin
      Member

      Hi,

      Issue confirmed. Issue added here: http://code.google.com/p/sqlyog/issues/detail?id=1579

      Thanks for reporting.

    • #31669
      peterlaursen
      Participant

      This is actually per design. 

      A query tab comes in  2 'flavors': 1) the 'normal' one 2) the 'special' one (sometimes it was called 'advanced'). In the 'special' one only *execute all* is possible.  This is because the 'special one' is used in contexts where executing a single query does no make sense. But the option to *execute current* should probably be disabled here.

      We also have the old discussion: http://code.google.com/p/sqlyog/issues/detail?id=280

      .. but frankly we did no agree internally what best solution would be. You are welcome to comment.

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