Tim,

Steve,

<<   There's a built-in script debugger in the EDB Manager that you can
use to set breakpoints, examine local variables, etc.  It's very helpful
with complicated scripts/procedures/functions/jobs/triggers.>>



I have wanted to ask this so many times, but I never did: would it require lot of work to
build an SQL script debugger integrated to the engine from what you already have?

Leslie

"Tim Young [Elevate Software]" wrote:

> Do you mean in a script ?  EDB scripts are a little more difficult to handle
> like this because they rely on executing from the begin to the end, and
> aren't just a series of SQL statements.

Sorry, yes I meant a script.  It's something I do often in the MS SQL Studio app.  In a stored procedure you can select a block of SQL and hit execute, and it executes
just the selected code.  I thought it would be handy to be able to do that with EDB Manager.  It's no big deal as I can work around it - just a suggestion.

Steve

Leslie,

<< I have wanted to ask this so many times, but I never did: would it
require lot of work to build an SQL script debugger integrated to the engine
from what you already have?  >>

You can see how it is implemented by looking at the EDB Manager source code.
It is already part of the engine, which is how we allow you to remotely
debug scripts using the EDB Server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Steve,

<< Sorry, yes I meant a script.  It's something I do often in the MS SQL
Studio app.  In a stored procedure you can select a block of SQL and hit
execute, and it executes just the selected code.  I thought it would be
handy to be able to do that with EDB Manager.  It's no big deal as I can
work around it - just a suggestion. >>

No problem.  I just see potential issues with uninitialized variables, etc.
if we don't execute prior statements that may be required by the selected
statements.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> No problem.  I just see potential issues with uninitialized variables, etc.
> if we don't execute prior statements that may be required by the selected
> statements.

Yes you have to remember to select all of the valid code, or copy and paste sections and
then select before running.  If there's anything missing it comes up with an error
message.  It is possible to get yourself into trouble though (he says, having done just
that).

Steve