Hi,

can it be that edbManager debugs code (simple query) which is commented out?

Regards Uli

Uli,

<< can it be that edbManager debugs code (simple query) which is commented
out? >>

Are you running a script ?  Also, are you commenting out the query *after*
executing the script ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<
Are you running a script ?  Also, are you commenting out the query *after*
executing the script ?
>>

No, just a simple query.
Do you mean after the first run? Maybe.
I posted a screenshot to the binaries.

--
Tim Young
Elevate Software
www.elevatesoft.com

Uli,

<< No, just a simple query.  >>

The debugging only works for scripts.  Queries can't really be debugged
because they're a single statement.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

>
> The debugging only works for scripts.  Queries can't really be debugged
> because they're a single statement.
>

ok, I understand. But edbManager complains when I run the query, like I
showed in the screenshot.

Uli

Uli,

<< ok, I understand. But edbManager complains when I run the query, like I
showed in the screenshot. >>

What were the steps that you took to do this ?  I just tried to recreate
this, and I can't really do so here.  I tried several combinations of edits
and undos, and the EDB Manager always executes the most current version,
i.e. it stops on the un-commented query, not the commented one.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> What were the steps that you took to do this ?  I just tried to recreate
> this, and I can't really do so here.  I tried several combinations of edits
> and undos, and the EDB Manager always executes the most current version,
> i.e. it stops on the un-commented query, not the commented one.

Hmmm. Difficult to say. I try to reproduce it and post it here.

Regards Uli

Tim,

it's like this:

/*
query1
*/
query2

if there is no error in query2, query2 is executed. If there is an error in query2, a line in query1 is highlighted.

Regards Uli

Uli,

<< it's like this: >>

Yep, got it.  It's an issue with the comments being stripped out of the SQL
being sent to the engine.

--
Tim Young
Elevate Software
www.elevatesoft.com