dbForge for MySQL newbie, downloaded an eval version of 4.0.224 two days ago.
I'm trying to use it debug a series of about 10 stored procedures. The processing is particularly long running and complex, so it is segmented by functional task and the procedures are executed in sequence. Temporary tables are produced in a procedure, then used by later procedures. This seems to work when the procedures are invoked either interactively with SQLYog or programmatically with C# via the MySQL Connector/Net.
But, when I try to use the debugger on the third procedure in the series, temporary tables produced by the first and second procedure are gone. I've experienced this when an error occurs; however, in this case there is no error.
What am I doing wrong?
Thanks in advance...
Temporary tables and the SP debugger
Hello.
We have tried to reproduce the bug and found no problem. Could you please tell us more information?
1. Does MySql server report that table doesn't exist while running third procedure, or you doesn't see the expected results of some operations under the table?
2. Are all procedures in the sequence compiled with debug information?
3. A sample of a code that reproduces the bug would be very helpful.
We have tried to reproduce the bug and found no problem. Could you please tell us more information?
1. Does MySql server report that table doesn't exist while running third procedure, or you doesn't see the expected results of some operations under the table?
2. Are all procedures in the sequence compiled with debug information?
3. A sample of a code that reproduces the bug would be very helpful.
Last edited by Elias on Wed 05 May 2010 08:25, edited 1 time in total.
1. It is a MySQL error (I think 1146 "table ... doesn't exist").Elias wrote:Hello.
We have tried to reproduce the bug and found no problem. Could you please tell us more information?
1. Does MySql server report that table doesn't exist while running third procedure, or you doesn't see the expected results of some operations under the table?
2. Are all procedures in the sequence compiled with debug information?
3. A sample of a code that reproduces the bug would be very helpful.
2. Is this a requirement? If so, is there a way to suspend the debugger's processing on the ones that I don't want to debug. They take a long time to run without the debugging...
3. Not a problem but will wait for your response before posting,
Thanks is advance.
1. Ok, so the table seems to be removed during the debugging. Unfortunatly we still fail to reproduce the problem.
2. No, of course this is not a requirement. But it will solve the problem with reaching timeout while execution of these procedures (a question from your letter). If you don't want to step into these procedures use operation Step Over to trace the code.
3. The sample would be appreciated.
2. No, of course this is not a requirement. But it will solve the problem with reaching timeout while execution of these procedures (a question from your letter). If you don't want to step into these procedures use operation Step Over to trace the code.
3. The sample would be appreciated.