Page 1 of 1
Connection property stored procedure debug error
Posted: Thu 03 Dec 2009 13:53
by dbrewerton
Hello, I'm trying to figure out why this is happening. I have compiled my SP with debugging. I start my procedure and the first line is fine. However when it gets to the breakpoint, I get that ugly error. Please help. THanks

Posted: Thu 03 Dec 2009 14:22
by Elias
Hello,
Could you please specify error text, dbForge for MySql version and MySql server version?
Error details
Posted: Thu 03 Dec 2009 14:56
by dbrewerton
Ok, the message I get is:
Connection property has not been initialized.
DBForge is latest version, 3.60.379.
MySQL Server version is 5.1.40-Community
Posted: Thu 03 Dec 2009 15:11
by Elias
We need some code sample to reproduce the error. Could you please send us your procedure?
Is the error reproduced permanently?
Error details & stored proc
Posted: Thu 03 Dec 2009 15:21
by dbrewerton
The error reproduces every time I run my SP in debug.
PROCEDURE vudatcom_egwtest.fixmytimes(IN RealTime TIMESTAMP, IN countit INT)
BEGIN
declare time1 TIMESTAMP;
declare Timevar TIMESTAMP;
declare firstrec INT default 1;
declare mycount INT default 1;
declare fixedtime TIMESTAMP;
declare maxslice INT;
SELECT MAX(slice_id) AS maxslice, slice_timestamp AS time1 from ewise_slice;
SELECT timestampdiff(MINUTE,time1,RealTime) INTO Timevar;
SELECT maxslice - countit INTO firstrec;
-- while mycount < countit DO
SELECT date_Add(time1,INTERVAL Timevar MINUTE) INTO fixedtime;
UPDATE ewise_slice set slice_timestamp = fixedtime where slice_id = firstrec;
set mycount = mycount+1;
set firstrec = firstrec+1;
-- END WHILE;
END
Posted: Thu 03 Dec 2009 16:10
by Elias
Thanks for the sample. We have successfully reproduced the problem. The problem caused by the statement:
SELECT MAX(slice_id) AS maxslice, slice_timestamp AS time1 from ewise_slice;
We will fix this error in the next build. To debug your procedure now you have to exclude such implicit cursors from the code. Sorry for inconvinience.
Posted: Thu 03 Dec 2009 16:20
by dbrewerton
So to successfully debug, I have to rewrite that line as:
SELECT MAX(slice_id), slice_timestamp from ewise_slice;
Do you have a timeline on the next release? I'm currently on a 30 day trial.
Posted: Thu 03 Dec 2009 16:39
by Elias
Unfortunatly you have to comment or remove this statement before debug, the debugger fails when trying to fetch the data from this cursor to the Data Window.
But, I have found a decision for you

. We have a public beta of a new version of dbForge Studio for MySql
http://www.devart.com/blogs/dbforge/?page_id=760
And the currrent build doesn't contain this error, but contains a lot of new features

. You can evaluate both products at the same time, and use dbForge Studio 4.0 for debugging your stored procedures.
New version
Posted: Thu 03 Dec 2009 17:11
by dbrewerton
Thank you, I will try it and give you feedback.
Oops, trial period expired???
Posted: Thu 03 Dec 2009 17:21
by dbrewerton
it says I have 0 of 60 days to try the beta.
Re: Oops, trial period expired???
Posted: Thu 03 Dec 2009 17:33
by Elias
dbrewerton wrote:it says I have 0 of 60 days to try the beta.
Ups, please send a request to our team using a form
http://www.devart.com/company/contact.html
with a link to this forum page and a short problem describe. We will try to solve the problem.
Posted: Fri 04 Dec 2009 10:38
by Elias
Hello, have you recieved our letter?