there is a good reason it looks alot like my code.... :)
owa_opt_lock was originally mine - many of the owa_* stuff in owa_util was, from 1995 way back when...
Your comment screen is really hard to use, the tab key doesn't take you from field to field naturally (you almost have to mouse) and the field icons take a bit of thinking to figure out what they are (no ALT tags?? took me a while to figure out the first one must be my name and the second must be my email address...)
Eddie Awad
· 3 years ago
Hi Tom,
OWA_UTIL is an old package indeed. In fact, by looking at the source code I see that its creation date was 07/09/95.
I appreciate your feedback regarding the comment form. All icon image tags do have alt attributes. But, I had to add the title attribute to make it work both in IE and Firefox. So, now if you hover your mouse over an icon, you should see a tooltip popup.
In any case, I have added text next to each field to make it clearer. I have also fixed the tab order of the fields.
I hope that will make it easier for you to comment in the future -- Thanks.
Thomas Kyte
· 3 years ago
Very nice - thanks Eddie - much more "clear" now (and tabbing works :)
Rob V
· 3 years ago
Why not just EXEC my_proc; ?
Eddie Awad
· 3 years ago
Sure, why not. They are basically the same to me:
<pre>SQL> exec my_proc ANONYMOUS BLOCK . called MY_PROC from line number 1
PL/SQL procedure successfully completed.
SQL> begin my_proc; end; 2 / ANONYMOUS BLOCK . called MY_PROC from line number 1
PL/SQL procedure successfully completed. </pre>
Petr Svoboda
· 2 years ago
The problem with this approach is that it tells me what package called my procedure but not which procedure or function inside that package. This information is not included in the stack. Any help here?
Sankar
· 2 years ago
If I use this in a member procedure of an object, I don't get the procedure name. I get the object name. Tom Kyte's link (who_am_i) also does not give the name of the procedure. How do I get this informatopn?
All Comments
there is a good reason it looks alot like my code.... :)
owa_opt_lock was originally mine - many of the owa_* stuff in owa_util was, from 1995 way back when...
Your comment screen is really hard to use, the tab key doesn't take you from field to field naturally (you almost have to mouse) and the field icons take a bit of thinking to figure out what they are (no ALT tags?? took me a while to figure out the first one must be my name and the second must be my email address...)
Hi Tom,
OWA_UTIL is an old package indeed. In fact, by looking at the source code I see that its creation date was 07/09/95.
I appreciate your feedback regarding the comment form. All icon image tags do have alt attributes. But, I had to add the title attribute to make it work both in IE and Firefox. So, now if you hover your mouse over an icon, you should see a tooltip popup.
In any case, I have added text next to each field to make it clearer. I have also fixed the tab order of the fields.
I hope that will make it easier for you to comment in the future -- Thanks.
Very nice - thanks Eddie - much more "clear" now (and tabbing works :)
Why not just
EXEC my_proc;
?
Sure, why not. They are basically the same to me:
<pre>
SQL> exec my_proc
</pre>ANONYMOUS BLOCK . called MY_PROC from line number 1
PL/SQL procedure successfully completed.
SQL> begin my_proc; end;
2 /
ANONYMOUS BLOCK . called MY_PROC from line number 1
PL/SQL procedure successfully completed.
The problem with this approach is that it tells me what package called my procedure but not which procedure or function inside that package.
This information is not included in the stack. Any help here?
If I use this in a member procedure of an object, I don't get the procedure name. I get the object name. Tom Kyte's link (who_am_i) also does not give the name of the procedure. How do I get this informatopn?