Debugging SP's

[simon_r2d2]

I have just brought the professional version of dbforge and am very happy indeed with it.

Just two niggles with debugging SP's that may have already cropped up.

Quite often, when I try to step into an SP I get an error 'result consisted of more than one row'. However, if I keep trying to step in, eventually the debugger starts properly...

Also, I have had the same problem as other users in that if I insert breakpoints and execute the SP, the breakpoints are ignored.

Any thoughts??

Simon

[Elias]

I have just brought the professional version of dbforge and am very happy indeed with it.

Just two niggles with debugging SP's that may have already cropped up.

Quite often, when I try to step into an SP I get an error 'result consisted of more than one row'. However, if I keep trying to step in, eventually the debugger starts properly...

Also, I have had the same problem as other users in that if I insert breakpoints and execute the SP, the breakpoints are ignored.

Any thoughts??

Simon

Hello, Simon, we are glad you enjoy the product.

The problem with message "result consisted of more than one row" is a known bug, it happens when user incorrectly breaks debugging by shutting down the MySQL server. You can fix it by redeploying the debugging engine, or by truncating the debugging tables manually.

About breakpoints, can you send us a sample of stored procedure in wich breakpoints are ignored?

[Elias]

We have fixed the problem with "Result consisted of more than one row" message during debugging. The fix will be available in the next build.