strange:: dual behaivour

osvald

Member²
I've got a two different results when i use Test Window for executing procedure. using 7.1.5.1397(96)

I've a procedure which gets data from one table (in cursor) and then checks (by PK) each value of cursor string with the target table if it founds values not equivalent then it makes update. one of values of cursor attribute is making by analytic function LAG, lets call it "flag";
no data change in source table.

when i use "start debugger(ctrl-F9)" -- procedure not making any changes -- it is ok (i said that no data change in source table), but if i pressing F8(execute) -- it change 1 row: value of "flag" (was 4 - now: 1) -- it's not right
then i again press "start debugger(ctrl-F9)" and value of "flag" correct's from "1" to "4": it's ok, and from this moment any execution by "start debugger(ctrl-F9)" -- making no change - it's ok too, but when i execute it by F8 -- it again making data in target table wrong.

I think it is not quite well behaviour of procedure execution, i never see in pl/sql developer before ?

I want to ask Marco to answer this question

sorry for my english -- you can ask me any q's to make situation clear.

thanks ;)
 
Can you send me a test case for this? Including the Creation DDL for any database objects that are involved?
 
sorry, it is difficult to replroduce this situation and give exact skripts but one new thing i've noticed (may be this is the reason)
is behaviour of procedure execution in TestWindow, e.g.:
--- Info ---

PL/SQL Developer
Version 7.1.5.1397
Windows XP Professional 5.1 Build 2600 (Service Pack 2)

Physical memory : 2
 
I see. This has to do with package state. When using the debugger, the package state is lost when executing the Test Script.
 
hmm, that's great =), I found that now I don't need to close and open TestWindow after I edit and compile PKG which I'm debuging.
thanks
 
Back
Top