variable reported as 'not a variable'

[ScottMattes]

This is starting to seep through to my conscience mind, but it seems like 'sometimes' variables are being reported as 'not a variable' when they haven't been set yet and then after they have been set their values will be displayed when I hover the cursor.

------------------
------------
Scott Mattes

 

[ScottMattes]

Just now I was paying real close attention and noticed that a variable defined at the top of the package body (i.e. it was global in scope) had a value when I entered a proc. Right after the proc set that variable to null the cursor hover and watch entry for it reported 'not a variable'. I let the proc run and right after the variable is set to a value the cursor hover and watch entry show the value.

Other variables, like cursor record fields, that are NULL show NULL for cursor hover and watch entry.

------------------
------------
Scott Mattes

 

[Marco Kalter]

I can only reproduce this "Not a variable" problem if the package spec is compiled with debug information and the nody is not (or vice versa). Do you also get this after explicitly adding debug information to the package by right-clicking on it and selecting "Add debug information" from the popup menu?

------------------
Marco Kalter
Allround Automations

 

[ScottMattes]

I saw this on code that I was working on. As far as I know the spec and body are always compile when I click the execute button.

How would I tell?

------------------
------------
Scott Mattes

 

[Marco Kalter]

You can check if an object is compiled with debug information by executing the following command:

select owner, object_name, debuginfo
from sys.all_probe_objects
where owner = user
and object_name =

The debuginfo column will be T(rue) or F(alse).

------------------
Marco Kalter
Allround Automations