feature request record def where were you born

[oraclelover]

This would be a really cool feature to have. Say I have the peice of code in a package labeled SAMPLE at the bottom. Now pv_eas_edd_rec was passed to the procedure from somewhere else which was passed to that procedure from somewhere else etc etc. I would like to right click or something on pv_eas_edd_rec and have it transverese the code to find the origin of pv_eas_edd_rec and show me the select statement that populated that record. As of now I can do a find on pv_eas_edd_rec and I end up getting hundreds of returns because this is used and defined all over the place. That's why the logic must snake through the logic to find the correct origin. That is going to the calling function or procedure and etc etc. Don't think about 100 packages in the system think of a system with 10,000 + packages. For smaller systems the find works great. For larger code bases it can not be as fast to find the origin as I would like. If I'm missing something let me know.

Thanks
SAMPLE CODE
IF pv_eas_edd_rec.edd_edit_cd = 'MIN_ASE_YEAR'

 

[ScottMattes]

hmmm, I know our little bitty systems isn't unique and in it you can get to a particular package unit from multiple paths.

The display (a treeview?) would have to show a list of end points and let you choose. This type of thing could open some eyes when code changes have to be made (say, is this going to adversely effect Billing if I make this change here for Personel?).

Maybe one of the inputs could be a desired end point?

 

[oraclelover]

shameless bump.

Sorry

 

[Marco Kalter]

I'm not quite sure what you are looking for. You want to know from where a specific function is called and where the parameter values are set?

 

[oraclelover]

I guess in a nutshell what I would like to see is what I would call a code road map. That is
I have proc1 proc2....proc100.
proc2 calls proc3 which calls proc 30 etc etc. Lets assume this goes 20 levels deeps with proc100 being the last to be called. I would like to right click on proc100 or something and see the pathway that led to proc100 being called. Does that make more sense? If I'm still not being clear enough I can maybe draw a image that would show what I mean more clearly.

Thanks

 

[Marco Kalter]

I see what you mean. This can be quite a large tree of course.