Cannot Alter Stored Proc Anymore – Green Arrow Disabled And F5 Does No

[standpoint]

I've been using the Free Community version 5.23 RC2 which I could Alter a stored proc and press F5. I just bought a single user Enterprise edition and now when I alter a proc, the green arrow is disabled and F5 does not work. On a newer version of the Free Community edition, the green “Execute” arrow is disabled there as well. Has this feature been removed?

[peterlaursen]

I will reply that that again!

Short answer:

–> Use the duble-arrow icon!

Long answer:

–> When you alter an SP from SQLyog a template script will be generated using the current SP code like

Code:

DELIMITER $$

DROP PROCEDURE IF EXISTS `test`.`rrrrrrrr`$$

CREATE DEFINER=`root`@`localhost` PROCEDURE `rrrrrrrr`()
BEGIN
select * from t4.blabla;
END$$

DELIMITER;

In here there are TWO SQL statements: DROP and CREATE (DELIMITER is NOT a SQL statement – it is a client-side control statement only!). To ALTER you have to 'execute all' – both DROP and CREATE. That is what the 'double green icon' is for.

In your old version the single and double green arrows did the same for the 'special' or 'advanced' tab type used for SP, VIEW etc. templates.

The only reason that this 'special tab' was introduced was that in the beginning the 'common' tab type did not handle DELIMITER.

Actually version 6.1 beta 1 will be released in a few days and there will then only be ONE tab type. There is no need for the 'special' one anymore as 'common' tab type works with DELIMITER. And both single-arrow and double-arrow icons will be available on all tabs. But you should note that also with this one you will have to 'execute all'. 'execute' (single-arrow) only executes the statement where cursor is positioned!

Was that understandable?

[standpoint]

Ok, but this is a change from 5.23 version where I can still press F5 on a stored proc tab and alter multiple statements. Shift+F5 works. I just have to get used to a new way. I was spoiled with the F5 shortcut since it's the same key to “execute” one or more statements in SQL Server. I know this sounds picky, but when I'm typing out a lot of sql code, it slows me down to have to go move the mouse and click vs. pressing F5. I'm still old school!

[peterlaursen]

I know that such changes can be annoying.

But it has also been confusing to some users that single-arrow in some contexts would 'execute all' – and a little dangerous actually. That is why we disabled it for the 'special tab' in 6.0 to tell users that ALL would be executed!

Basically I think what we do now is correct, and what we did originally was not.

[Author]

Posts