Cannot debug procedures

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
rdrbnhd
Posts: 2
Joined: Wed 02 Apr 2008 09:15

Cannot debug procedures

Post by rdrbnhd » Wed 02 Apr 2008 09:19

Hi,
I have installed MyDev and wanted to debug some procedures I have. It all worked fine till today, when I started getting an error message when I debug:
"Result consisted of more than one row". I thought it's something wrong i my code, but normal execution (without debug) worked fine.
So, I wrote a new small procedure with 1 line, and always I get this error.

Please advise,

Regards,
Dinka

Elias
Devart Team
Posts: 73
Joined: Tue 29 May 2007 14:02

Re: Cannot debug procedures

Post by Elias » Thu 03 Apr 2008 08:36

rdrbnhd wrote:Hi,
I have installed MyDev and wanted to debug some procedures I have. It all worked fine till today, when I started getting an error message when I debug:
"Result consisted of more than one row". I thought it's something wrong i my code, but normal execution (without debug) worked fine.
So, I wrote a new small procedure with 1 line, and always I get this error.

Please advise,

Regards,
Dinka
It's a known problem and we are working on it. Just redeploy the debug engine and everything will be ok.

rdrbnhd
Posts: 2
Joined: Wed 02 Apr 2008 09:15

Thanks, plus another question

Post by rdrbnhd » Thu 03 Apr 2008 09:16

Is it also known that when putting a label on a loop (e.g. while loop) debug fails?

Regards,
Dinka

Elias
Devart Team
Posts: 73
Joined: Tue 29 May 2007 14:02

Re: Thanks, plus another question

Post by Elias » Thu 03 Apr 2008 09:31

rdrbnhd wrote:Is it also known that when putting a label on a loop (e.g. while loop) debug fails?

Regards,
Dinka
Now we know about it.

Elias
Devart Team
Posts: 73
Joined: Tue 29 May 2007 14:02

Post by Elias » Mon 03 Nov 2008 16:30

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.

Post Reply