With the free TOAD (www.toadsoft.com) you can at least jump directly to the
proc/func that you want.
"Chris ( Val )" <chrisval_at_bigpond.com.au> wrote in message
news:b3v2qq$1qe666$1_at_ID-110726.news.dfncis.de...
>
> "Rene Nyffenegger" <rene.nyffenegger_at_gmx.ch> wrote in message
> news:b3t4me$1pkgn1$2_at_ID-82536.news.dfncis.de...
> |
> | >
> | > "Chris ( Val )" <chrisval_at_bigpond.com.au> wrote in message
> | > news:b3sumq$1pnu9v$1_at_ID-110726.news.dfncis.de...
> | >|
> | >| "Chris ( Val )" <chrisval_at_bigpond.com.au> wrote in message
news:b3sp7g$1q1t95$1_at_ID-
> | >|
> | >| [snip question]
> | >|
> | >| Hi everyone, I found what I was after, and that was: ALL_SOURCE.
> | >|
> | >| I'm still interested in any good books though :-).
> | >
> | > DOH!.
> | >
> | > It didn't work after all. Silly me had an existing procedure
> | > which wasn't in a package. That's where the view of the source
> | > code came from.
> | >
> | > Any ideas ?.
> | >
> | > Cheers.
> | > Chris Val
> |
> |
> | Chris
> |
> | You were nonetheless right about xyz_SOURCE.
> |
> | select text from xyz_SOURCE where type = 'PACKAGE BODY' and name =
'<package
> | name>' and so on. Unfortunatly, it's not possible look at a specific
> | procedure/function within the package without parsing the text of the
package
> | yourself (that is, I wouldn't know of a possibility). So, you can only
look at
> | the entire package.
>
> Hi Rene.
>
> That is unfortunate, however I appreciate the help.
>
> Cheers.
> Chris Val
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.454 / Virus Database: 253 - Release Date: 10/02/2003
>
>
Received on Mon Mar 03 2003 - 06:30:21 CST
