 | |
procedure: expand all input arguments
comp.databases.oracle.server comp.databases.oracle.server
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
procedure: expand all input arguments -
10-20-2010
, 10:57 AM
#2
| |||
| |||
|
|
Is there a generic way to expand all a procedure's input arguments. We'd like to create a general routine in our exception blocks that report all the procedure input argument names and values. *Unix shell has $*, or something like that; other languages have stack access, arguement arrays and such. Possible? |
use to get such information:
DBA_ARGUMENTS
ALL_ARGUMENTS
USER_ARGUMENTS
These will provide the argument names and passed values for packages,
procedures and functions.
David Fitzjarrell
#3
| |||
| |||
|
|
Is there a generic way to expand all a procedure's input arguments. We'd like to create a general routine in our exception blocks that report all the procedure input argument names and values. *Unix shell has $*, or something like that; other languages have stack access, arguement arrays and such. Possible? |
http://www.toadworld.com/BLOGS/tabid...eadcrumbs.aspx
jg
--
@home.com is bogus.
Oopsie! http://www.signonsandiego.com/news/2...oss-dressing-/
#4
| |||
| |||
|
|
On Oct 20, 11:57*am, okey <oldyor... (AT) yahoo (DOT) com> wrote: Is there a generic way to expand all a procedure's input arguments. We'd like to create a general routine in our exception blocks that report all the procedure input argument names and values. *Unix shell has $*, or something like that; other languages have stack access, arguement arrays and such. Possible? Not the way you want to do it, however there are three views you could use to get such information: DBA_ARGUMENTS ALL_ARGUMENTS USER_ARGUMENTS These will provide the argument names and passed values for packages, procedures and functions. David Fitzjarrell |
way to do it". Please suggest alternatives. We log errors in
production systems. We need more information to investigate these
errors. Collecting input values has been useful.
#5
| ||||
| ||||
|
|
On Oct 20, 4:32*pm, ddf <orat... (AT) msn (DOT) com> wrote: On Oct 20, 11:57*am, okey <oldyor... (AT) yahoo (DOT) com> wrote: Is there a generic way to expand all a procedure's input arguments. We'd like to create a general routine in our exception blocks that report all the procedure input argument names and values. *Unix shell has $*, or something like that; other languages have stack access, arguement arrays and such. Possible? Not the way you want to do it, however there are three views you could use to get such information: DBA_ARGUMENTS ALL_ARGUMENTS USER_ARGUMENTS These will provide the argument names and passed values for packages, procedures and functions. David Fitzjarrell Thank you David, but you're such a tease. * |
No, I'm not a 'tease'. I provided a starting point for you. It's up
to you to do the necessary work.
Quote:
|
What do you mean, "not the way to do it". * |
"Not the way you want to do it"
meaning there is no 'expansion variable' for procedure parameters. I
also provided three views to assist you in creating a way to report
those parameter values. Again, it's YOUR responsibility to do your
work.
Quote:
|
Please suggest alternatives. *We log errors in production systems. * |
what those parameter values are when an error occurs.
Quote:
|
We need more information to investigate these errors. *Collecting input values has been useful. |
post was vague on that point. When you provide more detail on what
you ARE doing then someone else can possibly suggest alternatives.
David Fitzjarrell
#6
| |||
| |||
|
|
On Oct 21, 9:32*am, okey <oldyor... (AT) yahoo (DOT) com> wrote: On Oct 20, 4:32*pm, ddf <orat... (AT) msn (DOT) com> wrote: On Oct 20, 11:57*am, okey <oldyor... (AT) yahoo (DOT) com> wrote: Is there a generic way to expand all a procedure's input arguments. We'd like to create a general routine in our exception blocks that report all the procedure input argument names and values. *Unix shell has $*, or something like that; other languages have stack access, arguement arrays and such. Possible? Not the way you want to do it, however there are three views you could use to get such information: DBA_ARGUMENTS ALL_ARGUMENTS USER_ARGUMENTS These will provide the argument names and passed values for packages, procedures and functions. David Fitzjarrell Thank you David, but you're such a tease. * No, I'm not a 'tease'. *I provided a starting point for you. *It's up to you to do the necessary work. What do you mean, "not the way to do it". * Show me exactly where I said that; my statement was: "Not the way you want to do it" meaning there is no 'expansion variable' for procedure parameters. *I also provided three views to assist you in creating a way to report those parameter values. *Again, it's YOUR responsibility to do your work. Please suggest alternatives. *We log errors in production systems. * As you should. *And now you have access to three views that can report what those parameter values are when an error occurs. We need more information to investigate these errors. *Collecting input values has been useful. And how have you been collecting those input values? *Your original post was vague on that point. *When you provide more detail on what you ARE doing then someone else can possibly suggest alternatives. David Fitzjarrell |
work some more on this. Thank you for putting me straight.
Joel - thanks fro your input too.
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.