Dubugging doesn't work

[zhekaus]

The only thing appealing me in dbForge is debugging functionality for stored procedures. However, I can’t make it work.
I was happy running it successfully once, and a little time after that it stopped working.
I again and again compiled my procedure for debugging, set break points in it, tried manually step into from the external script, read debugging instructions again – all in vain.
The only thing still working is step into from popup menu in database explorer that makes me enter parameters manually what isn't convenient.
However what I really want is stepping into from the external script or breaking running at the point inside the precedure.
Could anybody help me to understand what’s wrong?

[zhekaus]

I’ve found a workaround: I placed my script into the stored procedure. Now breakpoints are working.

It isn't convenient and led to two more issues:
1) Error messages happening during execution refer to the beginning of the stored procedure, but not to the sql statement generated an error. It makes debugging to be very tiresome.
2) SET FOREIGN_KEY_CHECKS=0 statement gives an error if the procedure compiled for debugging. However SET SESSION FOREIGN_KEY_CHECKS=0 works well. Odd.

[alexa]

Unfortunately, in dbForge, you can't step into a stored procedure from an external script. You can only step into a stored procedure from another stored procedure or trigger.

Though, you can add a suggestion on our UserVoice forum where other users can vote for it http://devart.uservoice.com/forums/7729 ... -for-mysql

We collect and analyze the information from this forum in order to make a proper roadmap for future product releases.

It isn't convenient and led to two more issues:
1) Error messages happening during execution refer to the beginning of the stored procedure, but not to the sql statement generated an error. It makes debugging to be very tiresome.
2) SET FOREIGN_KEY_CHECKS=0 statement gives an error if the procedure compiled for debugging. However SET SESSION FOREIGN_KEY_CHECKS=0 works well. Odd.

Could you please provide us the test data so we can reproduce the issues on our side?

You can send a reply straight to our support system at supportATdevartDOTcom

[zhekaus]

Thanks so much. I'll do it.