Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: all_triggers vs all_source (source code wise)

Re: all_triggers vs all_source (source code wise)

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Tue, 30 Apr 2002 16:45:20 +0200
Message-ID: <uctcfj66fddo40@corp.supernews.com>

"Marcel Kraupp" <marcel.kraupp_at_gmx.ch> wrote in message news:332bb004.0204300318.223e1b3d_at_posting.google.com...
> Hi
>
> Is there a reason why the source of triggers is stored
> in a long in all_triggers and the source of procedures/packages
> is stored in a varchar2 in all_source.
>
> Specifically, I wish there was a possibility to get a specific
> line of a trigger's body which doesn't seem to be easily possible
> without parsing.
>
> Or Am I missing a view which would help me into that direction?
>
>
> Marcel

No, you are not missing a view. Initially triggers were not compiled into p-code so they were treated differently. I wouldn't 'parse' these longs, when there are tools enough on the market that will do this for you. Toad (www.toadsoft.com) exists in a commercial and a (somewhat limited) freeware version. Even in this freeware version, it is still a Swiss knife.

Regards

--
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address
Received on Tue Apr 30 2002 - 09:45:20 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US