I’ve searched “:new.tipocodi” in all triggers of a single schema.
Results are corrects but same occurrence was signed twice.
Unique difference is in line number that is always incremented in 6 rows
Someone can help me ?
See below for more details:
11.57.58 Searching for “:new.tipocodi” in stored objects…
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No 47
or :new.tipocodi != :old.tipocodi then
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No 58
IF :new.tipocodi != :old.tipocodi THEN
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No 89
:new.tipocodi := TRIM(:new.tipocodi);
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No 90
if :new.coditabe is null or :new.tipocodi is null then
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No 105
UTILERRO.gesterroforo ( null, null,‘tipocodi:’||:new.tipocodi
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No 112
UTILERRO.gesterroforo ( null, null,‘tipocodi:’||:new.tipocodi
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No = 41
or :new.tipocodi != :old.tipocodi then
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No = 52
IF :new.tipocodi != :old.tipocodi THEN
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No = 83
:new.tipocodi := TRIM(:new.tipocodi);
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No = 84
if :new.coditabe is null or :new.tipocodi is null then
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No = 99
UTILERRO.gesterroforo ( null, null,‘tipocodi:’||:new.tipocodi
Found at > TRIGGER DATICOMU.PRE_INSUPD_CODI Line No = 106
UTILERRO.gesterroforo ( null, null,‘tipocodi:’||:new.tipocodi
Thanks for your feedback. For the purpose of this issue, I’m assuming you’re using Nav 5.5 based on information in your other post (please correct me if I’m wrong). Could you please send us the following:
A screenshot of the “What” tab in Code Search window (after you have done a search for “:new.tipocodi”). Please ensure that the window is big enough so that the screenshoot captures all the search results.
A screenshot of the “Where” tab in the Code Search window
A trace log of the search operation (you can start tracing just before you hit “Search”) using SQL Monitor or the trace functionality in Nav
Information on your Oracle client and server version
Also, would you mind doing a quick search on an object other than trigger (eg. procedure) and let us know if this doubling up also occurs ? Thanks !
I have collected many informations you need,
but not all, because i don't know sql nav "trace functionality" or "Sql Monitor".
Can you explain how i use these tools ?
Meanwhile, i send you information about point 1,2 (see attachs) and 4.
oracle client and server version is an Oracle 9i (9.2.0.1.0)
i'm working with a Sql Nav 5.5.0.713 Xpert Edition
no, i don't have problem when text is founded on others object type (see attachs)
Moreover, i send you an extract ddl for each object present in the result list (following piortek suggestions - hi piortek!)
I have collected many informations you need,
but not all, because i don’t know sql nav “trace functionality” or “Sql Monitor”.
Can you explain how i use these tools ?
Meanwhile, i send you information about point 1,2 (see attachs) and 4.
oracle client and server version is an Oracle 9i (9.2.0.1.0)
i’m working with a Sql Nav 5.5.0.713 Xpert Edition
no, i don’t have problem when text is founded on others object type (see attachs)
Moreover, i send you an extract ddl for each object present in the result list (following piortek suggestions - hi piortek!)
USER_TRIGGERS
and your code is inside both tables.
Numbers of lines are differend because users_source stores sqls as varchar2 and line numer is the number of single record of sql statement, user_triggers stores trigger body sa LONG, and numer of line is the real number of line of your code.
Regards Piter
Cry you are right!
Results are showed twice, because sqlnav search in USER_SOURCE
and
